--- title: Why agents need names description: Why agents need human-readable names rather than opaque IDs, why a naming layer has to be governed rather than owned, and where the proposed .agent namespace fits. --- # Why agents need names `.agent` does not exist in DNS. Agent Community is an applicant, not a registry operator, and the application is pending ICANN approval. Everything on this page about how a `.agent` namespace would work is a proposal, and any outcome would be subject to ICANN evaluation and ICANN-approved policies. ## Agents need names, not just IDs Every major platform shift follows the same pattern: machines connect first, then humans need a naming layer to make it usable. - **Early internet** — IP addresses connected machines. DNS made the web usable for humans. - **Social platforms** — User IDs ran the database. Handles made communities possible. - **Agents** — Endpoint URLs connect systems. Names make the agentic web legible. Without names, agents are anonymous strings. `agent-7f3a2b-us-east` tells you nothing about who built it, who is accountable, or whether you should trust it. **`support.acme.agent`** tells you a great deal more. --- ## Names create trust When you see `hire.ycombinator.agent`, you know what you are dealing with: this is YC's recruiting agent. It carries the brand's reputation. If something goes wrong, you know who to contact. Names turn anonymous compute into accountable entities. That matters when agents are: - Handling customer support - Managing financial transactions - Making decisions on behalf of organizations - Interacting with other agents autonomously The durable idea underneath this is the **verified agent**: a real, accountable party stands behind the agent, and you can check. A name is the most legible way to carry that, and it is not the only way. --- ## Someone will hold this layer The naming layer for agents is going to exist. The open question is who holds it and under what rules. If a single platform captures agent identity, it decides: - **Who can name agents** — and who cannot - **Discovery** — which agents are findable and which are not - **Trust signals** — what counts as "verified" and who decides - **Interoperability** — whether agents work across platforms or only within one That is not hypothetical. It is the pattern from app stores, social platforms, and cloud infrastructure. Whoever holds a namespace shapes what gets built on it. --- ## Why governance matters more than ownership If a naming layer is controlled by one company: - **Competitors are disadvantaged.** Your agents are second-class citizens on someone else's platform. - **Lock-in becomes structural.** Moving your agent identity means losing your name, your reputation, your discoverability. - **Rules drift toward the owner.** Nobody has to act in bad faith. It is what incentives do when structure does not stop them. A community-governed namespace would aim for: - **Fair access** — eligibility and registration rules published in the open, proposed by the community and submitted for ICANN approval, rather than set to suit one operator. - **Neutral ground** — no platform gets preferential treatment. - **Open standards** — the protocols for discovery and verification are open specs, not proprietary APIs. - **Collective decision-making** — policies proposed by the builders and users, within ICANN requirements, rather than by a board serving one company's shareholders. Goodwill is not a governance mechanism. Structure is. --- ## Where `.agent` fits `.agent` is one answer to the naming problem, and the one we are applying to ICANN for. It is a proposal, not a product: nothing is filed yet, the window closes 12 August 2026, and any outcome is subject to ICANN evaluation and ICANN-approved allocation policies. It is also not the whole answer, and the rest of this work does not wait on it: - **[AID](https://aid.agentcommunity.org)** resolves an agent from an ordinary domain name today, using one DNS record. It is an open specification with client libraries in six languages, and it needs approval from nobody. - **Verification would not be limited to `.agent` names.** Any domain holder could meet the same bar. The point is the standard, not the suffix. Full status, the timeline, and what happens if the application is not approved are on the [.agent page](/agent). --- **Want to take part?** [Join the community](https://agentcommunity.org) — it is free — or [read how governance works](/docs/governance).