Agent Community
agentcommunity.org | hello@agentcommunity.org | @agentcommunity_
What it is
We're applying to ICANN for the .agent top-level domain so it's run by the community, not a single company. 15,000 members and almost 4,000 companies have signed on. The analogy we keep coming back to: .edu is a signal that means education. .agent should be that for AI.
Who's in
| 15,000+ members | Developers, researchers, founders |
| ~4,000 companies | Alibaba Cloud, Datadog, Netlify, Brave, Sourcegraph, Ollama, Product Hunt, Convex, NEAR, Vapi, Composio, Resend, Factory, and growing |
| 6 SDKs | TypeScript, Python, Go, Rust, .NET, Java |
| IETF Internet-Draft | AID spec submitted to IETF Datatracker, March 2026 |
| ICANN window | Opens late April 2026 |
The problem
Every AI agent today is an anonymous endpoint string. There's no way to look one up by name, no portable reputation, no accountability. Someone is going to build the naming layer for agents. If it's a single company, they'll control discovery and trust for the whole ecosystem. We think that's the wrong outcome.
What we're building
The .agent TLD. A namespace where agents get human-readable names: brand.agent, product.agent, yourname.agent, support.acme.agent. ICANN's Community Priority Evaluation scores on size, diversity, and global reach. 15,000 members across companies, developers, and universities worldwide is the kind of profile that wins these evaluations.
AID (Agent Identity & Discovery). A DNS-based protocol. One TXT record at _agent.<domain> and any agent becomes discoverable. No central registry, no hard-coded endpoints. Works with MCP, A2A, gRPC, GraphQL, whatever. The spec is frozen at v1.2, already in production, and we've filed the IANA registration for _agent under RFC 8552.
Governance. Working groups set policy on registration, safety, verification, and tooling. Everything is public on GitHub. The people building agents decide how the namespace works.
Why it matters
The naming layer for agents is going to exist. The question is whether it's open infrastructure or owned by one company. A corporate-controlled namespace means one company decides who gets a name, how discovery works, and what the rules are. A community-governed domain means the people building and using agents set those policies together.
That's the difference between an open ecosystem where any agent can find and trust any other agent, and a walled garden where someone else controls the gates.
Where things stand
| Now | Next |
|---|---|
| 15,000 members, ~4,000 companies | ICANN application (submitting toward end of window) |
| AID spec stable, 6 SDKs, IETF draft filed | IANA registration of _agent label |
| Community governance being designed | Working group policy proposals |
| Backed by Alibaba Cloud, Datadog, Netlify, Brave, and others | Community Priority Evaluation |
| Agent Brief daily newsletter (news.agentcommunity.org) | TLD delegation and founding member access |
How you can help
Sign up and sign the endorsement letter at agentcommunity.org/join. Free, non-binding, 30 seconds. Every member makes the ICANN application stronger, and ICANN requires letters of endorsement from community members as part of the application, so we really appreciate every one we get.
Say so publicly. A tweet or post that you back community-governed agent identity reaches people we can't get to on our own. Tag @agentcommunity_.
Introduce us to your network. Partners, clients, communities in your ecosystem. We're submitting toward the end of the ICANN window, so every week between now and then counts.
Agent Community is an applicant for the .agent TLD, not a registry operator. All references to .agent are conditional on ICANN approval. Pre-registration is non-binding and does not guarantee domain allocation.