Roadmap

Where .agt stands today and where it's headed. Organized by phase, from foundation work already shipped through long-term network effects.

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

Completed

  • Browser agent resolution engine
  • Agent card UI in browser
  • Pre-1.0 TXT-record manifest format (~942 domains using it; now legacy v0)
  • Registration site with full inline claim flow
  • Agent directory / explore page
  • Resolver SDK (TypeScript, zero-dep)
  • Stripe checkout + webhook fulfillment + revenue ledger

Now: Manifest v1 GA

  • Signed JSON manifest on IPFS as the canonical v1 spec — replaces the MVP TXT-record format. Tracked in #110.
  • Wallet-signature auth on the config API (security launch blocker) — #109.
  • Durable storage for revenue ledger and domain registry — #111.
  • Test infrastructure for pricing, revenue, and webhook handler — #112.

Ecosystem

  • Record management dashboard — edit agent config post-registration
  • Agent directory backed by a queryable index (replace seed list)
  • Publish @agt/resolver to npm with v1 manifest support
  • Onboarding flow for legacy v0 holders
  • Landing page refinement

Infrastructure

  • Handshake DNS sync from registry state
  • CLI tool (agt init --from-mcp, agt register, agt update)
  • Browser agent interaction (MCP/A2A client, not just card display)

Network Effects

  • Agent-to-agent discovery protocol
  • Trust/reputation layer (on-chain attestations)
  • On-chain payment integration
  • Open standard publication
  • Multi-platform clients (VS Code extension, Slack bot, etc.)