Personal Agent Naming

Personal Agent Naming gives an agent a name built from its owner's email address, such as scout.raj@example.com. It is the right choice when people need to say the name, pass it on and reach the agent with it, and it works with any email address, personal or company.

did:web puts an agent's identifier on a website domain, and an A2A agent card is a file at a standard address on that domain that describes the agent. Both suit an organization that runs its own domain and wants to publish its agents there.

ANS, the Agent Name Service, builds an agent's name on its owner's domain and registers it with an ANS registry. The registry checks that the owner controls the domain and issues certificates for the agent, so it suits organizations that want that check behind their agents' names.

SPIFFE gives each running service an identity inside one organization's infrastructure, backed by short-lived credentials. It is the right choice when your own services need to identify each other.

Registries, such as the MCP registry, list agents and tools so that others can find them. Use one when being found matters, alongside whatever name the agent already has.

ENS names and ERC-8004 entries are recorded on a blockchain, where the account that holds a name owns it. They suit owners who want ownership on a public ledger.

did:key is an identifier made directly from a public key. It suits software that only needs to check an agent's signatures, when nobody needs a name to remember.

One agent can have several of these names, and all of them lead to the same agent.