Open · DNS-native · No gatekeepers
> The DNS of the agentic web

One domain. One zone file. Every agent capability — agents, MCP servers, skills, A2A endpoints — discoverable and verified via DNS.

agentroot
$ npx agent-root search database --type mcp domain type name ────────────────────────────────────────────── acme.io/db-tools MCP DataTools sql.dev/query MCP SQL Query data.co/analytics MCP Analytics $ npx agent-root install acme.io/db-tools DNS verification passed MCP config generated for Claude Code 3 tools available: query, visualize, export $
Works with

// the_trust_problem

In the age of agents, provenance is everything.

AI agents are about to use tools on your behalf — calling APIs, moving money, accessing data. The question isn't "what can this skill do?" It's "who published it?"

When an AI agent finds a skill called "payments", how does it know it's legitimate? A GitHub username doesn't prove anything. An npm package name is just a string. But a domain? That's identity you can verify.

stripe.com has been Stripe's domain since 2010. It's in the internet's public directory. Nobody can fake it. Nobody can squat on it without being caught. Domain ownership is the strongest proof of identity on the web — and AgentRoot uses it as the foundation for trust.

One DNS record. That's your declaration of existence. We read it, verify it, and make your skills discoverable to every AI tool on the planet. No accounts. No gatekeepers. No approval process.

Which one do you trust?
stripe.com/skills/payments.md
random-guy.com/stripe-payments/SKILL.md

Domain ownership is the identity layer the agentic web needs. AgentRoot makes it the foundation of skill discovery.


// use_skills.sh

$ use skills — one command, any tool.

Find skills in the registry and install them with a single command. Works with Claude Code, Codex CLI, Gemini CLI, Cursor, and more.

$ npx agent-root install stripe.com/payments
# auto-detects your AI tool, downloads the skill, ready to use
# Personal (all your projects) npx agent-root install stripe.com/payments --tool claude # Project-scoped (shared with team via git) npx agent-root install stripe.com/payments --tool claude --project
# Global npx agent-root install stripe.com/payments --tool codex # Project-scoped npx agent-root install stripe.com/payments --tool codex --project
# Project-scoped (cross-tool standard) npx agent-root install stripe.com/payments --tool gemini # Works alongside Codex CLI skills npx agent-root install stripe.com/payments --tool gemini --project
# Downloads to .cursor/skills/ npx agent-root install stripe.com/payments --tool cursor # Reference from your .cursorrules file
$ ls /registry → $ use skills — full guide →

// publish.sh

$ publish your zone in 3 steps.

Have agents, MCP servers, or skills? Declare them all in one zone file. No accounts. No approval. Just DNS.

01

Create a zone file

One JSON file listing your agents, MCP servers, skills, and A2A endpoints. Host it at .well-known/agentroot.json.

02

Add a TXT record

One DNS record: _agentroot.yourdomain.com pointing to your zone file. Takes 2 minutes.

03

Submit & done

AgentRoot verifies your DNS, fetches your zone, indexes all records. Discoverable everywhere.

$ publish → SKILL.md spec →

// why_dns.md

Built on the web's oldest infrastructure.

DNS has been running for 40 years. It's decentralized, public, and already trusted by every device on earth. We're using it — not replacing it.

Decentralized

No single company controls this

DNS is the internet's public directory. No one owns it. Your domain, your skills, your rules.

Verifiable

Domain = identity

If you control the domain, you control the skills published under it. No impersonation possible.

Multi-type

Agents, MCPs, skills, A2A

One zone file declares everything. Like DNS has A, MX, and TXT records, AgentRoot has agent, mcp, skill, and a2a records.

Hierarchical

Domains & subdomains

Each domain is a zone. Subdomains get their own zones. Independent but coherent — just like DNS delegation.


// roadmap.md

Where this is going.

Building the discovery layer for the agentic web. Openly.

live
Zone model — agents, MCPs, skills, A2A in one zone file
One _agentroot TXT record. One zone file. All your agent capabilities — agents, MCP servers, skills, A2A endpoints — indexed and discoverable.
next
Automatic zone file ingestion
No submission needed. AgentRoot reads the internet's public directory automatically — publish a DNS record and you're found.
v3
Semantic search
Find capabilities by what they do, not just their name. "Find me an MCP server that queries databases."
v4
Decentralized nodes
Anyone can run their own AgentRoot node. The registry becomes a network, not a single point of control.