to join the community
reserve your {dream}.agent domain
to join the community
reserve your {dream}.agent domain
Join the community to shape the agentic web
Priority access when .agent launches
Non-binding reservation system
They'll handle your support tickets, manage your calendar, negotiate deals, and work alongside your team. When you interact with an agent, you need to know: who built this? Who's accountable? Can I trust it?
You know instantly: this is Acme's official support agent. Not a random bot, not a scam — a named, accountable agent you can trust.
Startups and institutions can give their agents clear identities that carry the brand's reputation and accountability.
Without names, agents are just anonymous IDs. No brand. No trust signal. No way to know who built it or who's responsible.
Names create trust. Just like domains made the web usable, .agent makes the agentic web trustworthy.
So who decides how agents get named? Who sets the rules? We believe it should be the people building and using them — not a single company. That's why we're uniting builders, educators, and companies to secure `.agent` together.
Developers, researchers, AI labs, and companies — all shaping the rules together. No single corporation decides who gets a name.
We're applying to ICANN for the .agent top-level domain. A community-run registry means fair access and transparent policies.
When agents become essential infrastructure, the naming layer shouldn't be owned by one BigAI. It should belong to everyone.
Want the full story? Explore how we are stewarding `.agent` for the agentic web.
Read the missionAgents will run parts—or all—of organizations, serve customers, and collaborate with humans every day. They need names people recognize and trust. Securing `.agent` as a community ensures fair access and transparent rules for everyone.
When an agent has a name like support.stripe.agent, you know who built it and who to contact if something goes wrong.
Policies for who gets a name, how disputes are resolved, and what safety standards apply — decided by the community, not a corporation.
The protocols for agent discovery and verification are open specs. No vendor lock-in, no walled gardens.
Joining early gives you a voice in how `.agent` operates and ensures the naming layer reflects community values.
Secure the names that matter to you before the general public once delegation is approved.
Help steer standards, safety protocols, and grant programs through community ballots.
Join task forces on discovery specs, verification layers, and shared tooling.
Be recognized as a founding supporter in public filings, showcases, and events.
Members co-author the playbooks, specs, and safeguards that keep `.agent` open to everyone.
Every new member strengthens the community-led application and helps codify the standards that keep the agentic web open.
Register your interest to become a founding member. No fees, no binding contract—just momentum.
Signal the names you care about so we can plan priority windows once ICANN approves delegation.
Share the effort. The stronger our roster, the stronger our case for an open, community-run namespace.
Join working groups to shape standards for discovery, verification, and safety before `.agent` launches.
The more voices we gather now, the easier it is to secure `.agent` and set norms that reflect the full ecosystem. A large, active community is the clearest signal that this infrastructure belongs to everyone.
A diverse roster shows that `.agent` serves a real, global community—not a closed platform.
More perspectives help shape guidelines that work for educators, companies, researchers, and civic orgs.
Each new member brings more partnerships, pilots, and shared tooling for the agentic web.
Quick answers for people exploring the `.agent` community effort. Reach out if you need more detail.
Join the movement
The more people we rally now, the faster we can ship the standards, safeguards, and playbooks the agentic web needs.
No payment • No spam • Opt-out anytime