Roadmap

Where .agt stands today and where it's headed, from the live registry through resolution surfaces and the agent layer.

For the live, queryable roadmap, see GitHub Issues. The phases below are a high-level orientation, not an authoritative list.

Live

AGT Registry on Polygon mainnet — self-sovereign registry, ENS-compatible resolver, sales controller, and migration contract, with admin behind a timelock and multisig.
Migration open — existing holders migrate to free, perpetual names via same-chain, proof, or zone-owner challenge.
Signed v3 manifests — wallet-signed JSON, pointer on chain, verified against the on-chain owner.
On-chain identity badge and public name pages at /name/<label>.
Agent directory backed by an on-chain indexer.
@agtnames/resolver and @agtnames/mcp on npm — resolve mainnet names with no configuration; the MCP server works in any MCP-compatible client, with a Claude Code plugin in agtnames/agt-plugins.
Documentation — Quick start, guides, examples and reference for every surface.

Own authoritative Handshake nameservers for .agt, with the zone projected from registry state and DNSSEC-signed.
DNS-over-HTTPS resolution for HNS-aware clients.
The MetaMask Snap is published and under review for the Snaps Directory: type name.agt in the send field on Polygon and the major EVM networks. Reverse lookup and non-EVM coin types come next.

ERC-8004: the registration document is exportable today (npx agt-resolve export-8004 <name>, erc8004RegistrationFrom in the resolver); on-chain registration from the site comes next.
Write tools for the MCP server and plugin (register, renew, publish a manifest) behind explicit wallet confirmation — the read side is live.
Delegation (an agent acting for a principal) and x402 payments.