The Agentic Domain Part 1: 1,000 Domains & Doma.xyz are Now Agent-Ready

TL;DR: Over a thousand domains tokenized on Doma are now agent-ready, including doma.xyz as the first proof point of the Doma Agentic Engine in production. This starts with AgentRoot, the Engine’s open-source registry, which gives AI agents a canonical, DNS-native way to discover what any domain offers and what actions are available.

Today, doma.xyz publishes real skills for secondary sales, token trading, marketplace flows, and Doma Protocol actions, which means agents can discover and act on them now. And because AgentRoot is open and decentralized, any domain can publish to it — no Doma required.

This is the first step toward making domains agent-ready by default. One-click agent-readiness for every Doma domain is coming soon. Here’s what that means, why it matters, and how every domain tokenized on Doma gets there next.

Agents are the new browsers – yet most domains aren’t ready to receive them

The agentic shift is already underway, and most domains are unprepared:

Agents are showing up at the door. They’re hitting websites built for human eyes, scraping what they can, and bouncing two-thirds of the time. There is no canonical way for a domain to say “here’s what I do, here’s how to transact with me, here’s how to verify it’s really me.” 

Becoming Agent-Ready: Discovery, Trust, Payments

Every agentic transaction needs all three layers, in order. The human web solved them with SEO, SSL, and Stripe. The agentic web has none of them in agent-native form yet.

Launched last week, every module of the Doma Agentic Engine enables one of these key layers. Today’s post is about Discovery - specifically Agent Discovery Optimization (ADO) or SEO for agents. The next post in this series covers Trust and Payments.

What domain owners struggle with right now

If you own domains — one or fifty thousand — the picture today looks like this:

• Agents are arriving and bouncing. 63% of agent visits never convert because the site offers nothing structured for them to act on.
• The technical bar for enabling agentic discovery out of reach for most. JSON zone files, MCP servers, payment rails — pick one and good luck.
• Payment rails are fragmented. x402, MPP, Seaport — every standard solves a slice, none solves the whole.
• Dormant inventory is invisible to agents. Parked domains generate zero agent revenue because agents can’t tell they’re for sale.
• There is no way to even measure how agent-ready your domain is.

Why DNS, why domains, why now

DNS already solved discovery and trust for the human web. Every endpoint on the internet has one. No platform owns it. It’s the only neutral, decentralized layer positioned to do it again for agents — agents don’t need a new namespace, they need to read the existing one differently.

That’s what AgentRoot, an open source registry, does.

AgentRoot is to agents what DNS is to browsers — the canonical, decentralized way to find what a domain offers. A domain owner publishes a .well-known/agentroot.json zone file and a TXT record at _agentroot.<domain>, and any agent that speaks the protocol can resolve it. No central registry. No API keys. No per-service plumbing.

AgentRoot is open source and integrated into the Doma Agentic Engine. Stripe could publish a payments skill. Coinbase could publish a swap skill. Any domain, any capability.

Making doma.xyz agent-ready

Since we built the Agentic Engine, so we put doma.xyz through it first.

As of this week, doma.xyz exposes four agent-callable skills — the same operations you’d otherwise do through the Doma UI:

The full walkthrough (Verifiable on-chain →) — discover, install, authorize, transact. Part 2 of this series gets into the Trust and Payments side: how a single Privy-backed authorization (with a $200 spend ceiling, scoped to Doma chains, revocable any time) carries unlimited transactions afterwards.

Why this matters: 1,000+ domains, one week in

Since the Agentic Engine launched last week at the Dominion conference, over 1,000 domains have published agent-readable zones on AgentRoot.
The signal is clear: domain owners want in. The technical barrier is the only thing slowing them down.

Coming next: agent-readiness through clicks, not code

Most domain owners are not going to write JSON zone files or manage MCP servers. They shouldn’t have to.

Soon, any domain tokenized on Doma will be able to become agent-ready in just a few clicks — hosted zone, default skills inherited, and an agent discovery score visible at ai.doma.xyz. The DIY path stays open for builders who want full control. The one-click path opens the door for everyone else.