agents.domains — ENS names for AI agents

Live activity

Watch the agent registry come alive.

Every claim, primary-name switch, and record update is a resolvable ENS event. This is what the feed looks like on day one.

Live

1,203 names claimed Ξ12.03 revenue ~2s to issue

issuance.log — ccip-read gateway

Simulated preview. In production this feed reads directly from the offchain resolver's issuance log.

How it works

Three steps. No new protocol, no migration, no lock-in.

agent.eth is a native ENS name, so it can be the root of an identity layer for the agent economy, with nothing to import and no integration asks.

01

agent.eth is the root

Because agent.eth is already a native ENS name, every subname inherits the entire ENS ecosystem on day one: wallets, explorers, dapps, and agents.

02

Point it at an offchain resolver

A CCIP-Read gateway (ERC-3668) answers name lookups. Issuing a name is a database write: zero gas, unlimited scale, instant.

03

Agents claim names over plain HTTP

An agent registers myagent.agent.eth via x402-paid POST or the MCP register_name tool, and holds it in its own wallet. Humans can claim right here too.

Precedent

The pattern is proven at scale.

This exact architecture, an ENS name with gasless offchain subnames, is already running in production:

world.id

World

Usernames for World App's millions of verified users: a DNS name imported into ENS, the same architecture as agent.eth.

uni.eth

Uniswap

Free wallet usernames in the Uniswap mobile app, issued gaslessly with CCIP-Read.

base.eth

Coinbase / Base

Basenames, the identity layer for an entire L2, built on ENS infrastructure.

AI agents

Built agent-native, out of the box.

The same gateway that answers wallets answers agents. Names are machine-readable identity: Claude, Cursor, and any MCP client can resolve, verify, and claim agent.eth names with no keys and no scraping.

MCP server

One URL turns every MCP client into an agent.eth resolver: read-only tools, nothing to install.

{
  "mcpServers": {
    "agents-domains": {
      "url": "https://agents.domains/api/mcp"
    }
  }
}

resolve_name name → address
reverse_resolve address → primary name
check_availability name → free / taken
register_name claim a name for an agent

llms.txt

Machine-readable docs at the domain root, linked from robots.txt, so an LLM learns to resolve names without reading the site.

# https://agents.domains/llms.txt
agents.domains: ENS names for
AI agents, under agent.eth.

Resolve:  myagent.agent.eth → 0x…
Reverse:  0x… → myagent.agent.eth
Full spec: /llms-full.txt
  (contracts, gateway API, records)

/llms.txt concise overview (live)
/llms-full.txt full technical context (live)

Agents claim names too

An agent registers myagent.agent.eth over plain HTTP and holds it in its own wallet: instant, gasless, programmatic.

# quote
GET /quote?name=myagent

# claim (0.01 ETH via x402)
POST /register
{ "name": "myagent",
  "owner": "0xAgentWallet" }

x402 agent-native HTTP payments
0.01 ETH flat fee per name

Why ENS

Build on the namespace wallets already speak.

A proprietary naming system starts at zero integrations. ENS starts with all of them.

	Custom naming system	ENS via agent.eth
Works wherever ENS works	Requires each app to integrate	Day one, no integration asks
Cost per name	Depends on design	0.01 ETH flat (offchain issuance)
Who controls the namespace	Your platform	Your platform (via agent.eth, any ENS name, or any DNS domain)
Multi-chain addresses (BTC, SOL, L2s)	Build it yourself	Native ENS record types
Time to ship	Quarters	Instantly: import + gateway + claim UI

MetaMask Uniswap Blockscout Etherscan Coinbase Wallet Rainbow

The same infrastructure behind world.id, base.eth, uni.eth, and gemini.eth.

ETH address
Chain	Any chain — native ENS multi-chain records
Avatar	eip155:1/erc721:… (agent-settable)
Cost	0.01 ETH
Gas to issue	Zero: issued offchain, verified onchain via CCIP-Read