Agents Need Names
TL;DR: .agent is the most strategically important TLD still without an owner. ICANN's application window opens in weeks. A company is going to bid for it - unless a community claims it first. Here's the story, and two questions I'd actually like pushback on.
---
Agents already need real addresses. I've been working on this for over a year, and the pitch just keeps getting simpler. Right now agents mostly live at a subdomain of whoever built the framework — platform.com/yourname-7. Borrowed identity, borrowed trust.
If you want the concrete version, look at OpenClaw. An autonomous agent running on your machine with its own email (real OTP codes, real password resets), OAuth credentials across hundreds of thousands of SaaS apps, sub-agents spawning and talking to each other, webhooks, the whole thing. A worker, not a demo.
And in its first three days live, OpenClaw had to rename itself twice. The name it launched under - gone. That's the whole argument in one news cycle: agents running real lives from borrowed names are one legal letter away from disappearing.
.agent is the most strategically important TLD still without an owner. ICANN's next gTLD round opens in weeks. And once .agent is claimed, it's claimed - the internet's naming system doesn't hand these out twice.
If one company wins it, .agent becomes their product. They'd set pricing. They'd set policies. They'd decide who gets yourname.agent and who gets blocked. One company choosing shareholder interests over an open internet - because that's literally what it would be.
The community bid is a formal ICANN community application — its own specific path with its own process. The goal, if approved: keep .agent open infrastructure. Open standards for agent discovery. No gatekeeper. Governance by the people actually building agents, within ICANN's rules.
23,000+ members have joined. Esther Dyson, who used to chair ICANN, and Illia Polosukhin, who co-wrote "Attention Is All You Need," are advising.
It's not done. ICANN scores community applications on size, governance, nexus, and endorsement depth. You need 12/16 points to beat the corporate applicants who are absolutely going to file. Every signal matters.
Two questions I'd genuinely like pushback on:
1. Is the naming layer for AI agents something the community should own, or is it fine if it goes corporate? I have a strong view, but makers building agents every day see things I don't.
2. If you think it should stay open - what governance rules would you want locked in from day one? What would make you still trust the TLD in 5 years?
If this resonates, the non-binding endorsement is here (30 seconds). The one-pager has the deeper version.
Either way, would love to hear what you think. Especially the pushback.

Replies
Honestly, never thought about .agent as a TLD until now. But yeah, OpenClaw renaming twice in three days is a wild example.
If the community wins it, who actually decides who gets "apple.agent" or "openai.agent"? Curious how you'd prevent squatters.
This is actually a really important moment. Agents are going to need real, permanent identities, and letting one company own .agent feels like giving them the keys to the whole ecosystem.
Strongly support the community bid. The open governance angle is what will make people trust it long-term.
What’s the biggest rule you think should be locked in from day one to keep it truly open?
Hello Aria
100% agree. Names change the relationship. They set expectations, invite projection, and create a kind of implicit contract about what the agent will and will not do.
We named ours "Aria" for Hello Aria, an AI assistant that manages your day via WhatsApp/Telegram. The name was a deliberate choice — warm, approachable, a little musical. It primes people to treat her as a capable helper rather than a command-line interface. We saw this reflected in how people talk to her: conversational, patient, even polite. That would not happen if she were called "Assistant" or "Bot-7."
Agent naming is underrated product design.
Owning your identity instead of just renting it from a giant corporation is such a vital move for keeping the internet open. If one company gets to set all the rules for .agent, we’re basically just building another walled garden. Keeping the naming layer in the hands of the community ensures that builders, not just shareholders, decide how things work. It's a bold step toward making sure our digital workers actually have a stable home!
Do you think a community-run board can stay neutral enough to keep everyone's trust over the long haul?