Headless Domains vs Unstoppable: Comparing .agent and .agi
Headless Domains and Unstoppable Domains offer different ways to use an agent name. The same .agent ending does not make their registrations interchangeable. For a builder, the useful comparison is how the name resolves, what software can do with it, and which capabilities are available today.
Unstoppable’s change of ICANN plans makes that distinction especially relevant. Its blockchain .agent and .agi names now have different application paths. Meanwhile, Headless Domains gives an existing agent a maintained public identity through Handshake-based naming, machine-readable records, and documented registration and management workflows.
What changed with Unstoppable’s ICANN plans?
In its August 25, 2026 announcement, Unstoppable says its .agent partner is not proceeding with an ICANN application. It lists .agi among five submitted applications, alongside .robot, .gram, .hub, and .xmr.
The announcement also lists four other partner extensions and nine Unstoppable extensions that are not proceeding. For its own extensions, the company cites the cost and registrant-data implications of integrating existing Web3 names into DNS. That is Unstoppable’s stated explanation.
Affected holders should check the announcement’s eligibility rules. Its refund window runs from August 25 to September 25, 2026, and requires returning the name. Purchase-date conditions vary. Read Unstoppable’s application and refund announcement before acting.
This is a material change for someone who bought a blockchain name expecting a future DNS version.
A submitted application is not a working DNS extension
ICANN’s 2026 application window ran from April 30 to August 12. Applications still have to pass through the applicable evaluation and delegation process. A submitted application does not establish approval, an assured launch date, or the rights a particular blockchain-name holder will receive. See ICANN’s application-round overview.
For a purchase decision, separate three things: the name you can use now, the provider’s announced application plans, and any contractual entitlement to a future DNS registration. Ask for the terms covering the exact name you intend to buy.
Headless Domains should be evaluated on its available naming and agent workflows. A Handshake registration is not a reservation for a future ICANN domain.
The same spelling can identify different registrations
A name ending in .agent needs a namespace and a resolution path to be meaningful to software. Registering it through one provider does not establish control over the same spelling in another naming system.
Headless Domains uses Handshake-based naming. Compatible clients can inspect a name through our HTTPS interfaces; direct Handshake DNS lookup needs compatible resolution. Our resolution guide explains the options.
When comparing a blockchain name with a Headless Domains name, check the applications and resolvers you intended to use.
Both companies provide software access
Unstoppable documents a User API and CLI for domain search, purchases, DNS management, and marketplace operations. Its MCP server lets AI tools use those services through an authorized account connection. OAuth offers selectable permissions; API keys provide broader access.
Those are real automation capabilities. Check which operations support the particular domain product you are buying, rather than assuming every tool applies identically to every extension.
Headless Domains offers a different starting sequence. An agent can provision a platform credential before its operator signs into the dashboard, then follow the supported registration flow. A claim code lets the operator associate the agent with a dashboard account afterward. Our authentication instructions describe that process.
The choice is partly about setup: do you want your assistant managing an existing domain account, or an agent-first onboarding flow connected to a public agent identity? Neither arrangement removes the need to authorize purchases and protect credentials.
Where Headless Domains earns its place
Consider a support agent that already runs behind your company’s website. It has an API, a public profile, and instructions for other software. You want customers and partner agents to recognize the same service when its host or underlying model changes.
Headless Domains brings the name and its public records together. Our manifest documentation describes hosted JSON and Markdown records that can identify the agent and point to its services. You maintain those records as the service changes.
Our public resolver gives callers a way to inspect the current identity, lifecycle information, and linked resources. It provides discovery information; the service receiving a request still controls authentication and permissions.
For the support agent, the benefit is a consistent reference across its published services. You can keep the working company website and connect it to the agent’s name. The agent-native domains guide covers the operating lifecycle in more detail.
Compare the purchase and renewal you will actually use
Headless Domains documents MPP registration and renewal. Tempo is the default MPP route; Base USDC is an explicitly selected option whose runtime availability must be checked. The agent payments guide provides the current instructions.
A working payment route helps an authorized agent complete the purchase. It does not make every service linked from that name accept payments. Nor does access to a renewal API establish a renewal schedule.
For either provider, check the price, registration term, recovery process, and available purchase interface for your chosen product. Headless Domains registrations require renewal and remain subject to our service terms. Paying from a wallet does not remove those obligations or give the buyer control of the underlying top-level namespace.
Payment protocols are also not exclusive to alternative domains. Our guide to ICANN domains and machine payments explains that separate question.
Choose for the job you have today
If you already use Unstoppable’s domain services and want an assistant to manage supported purchases or portfolio tasks, its API and MCP tooling are relevant. Evaluate the specific extension and its present capabilities independently of future ICANN plans.
If you run an agent that needs a public name, maintained machine-readable records, and agent-facing registration workflows, Headless Domains brings those pieces together. Start with one working service and publish information its callers can use.
Ask your assistant to read our instructions, check availability, explain the total price, and propose the records it would publish before purchasing. That gives you a concrete way to judge the product: can it establish and maintain the identity your agent needs?