User Flows

How users, developers, and agents interact with the .agt ecosystem — from claiming a name to programmatic resolution to agent-to-agent discovery.

Flow 1: Claim a Name

The registration site at /claim walks users through:

  1. User visits /claim.
  2. Types a name (e.g., "researcher"), clicks Search.
  3. API checks availability and shows the price.
  4. User enters a wallet address (0x...).
  5. Clicks "Claim this name."
  6. Backend creates the zone, triggers minting, and sets the agt-version=1 sentinel record.
  7. Frontend polls minting status every 5 seconds.
  8. On success, the AgentConfigForm appears.
  9. User fills in: name, description, protocols, capabilities, and endpoints — or clicks "Skip for now."
  10. Backend writes the manifest. Today: legacy v0 TXT records. v1 will serialize signed JSON to IPFS and write a single agt-manifest=ipfs://{cid} pointer (tracked in #110).
  11. Done screen: domain claimed, config status, and next actions.

Flow 2: Browse an Agent from the Browser

  1. User types exampleagent.agt in the browser URL bar.
  2. TLD hint routes to the public .agt resolver.
  3. Resolver returns TXT records.
  4. Parser finds agt-version=1 and extracts all agt-* records into a manifest.
  5. Frontend renders an agent card (not a webpage).
  6. User sees: name, description, protocols, capabilities, and endpoints.
  7. Clicking an endpoint opens it in a new webview tab.

Flow 3: Resolve Programmatically

Using the @agt/resolver SDK:

import { resolveAgent } from '@agt/resolver'

const agent = await resolveAgent('exampleagent.agt')
if (agent) {
  // Use agent.endpoints[0].url to connect
  // Check agent.protocols for supported communication methods
  // Read agent.capabilities for what it can do
}

Works in any JavaScript runtime. The SDK calls the public .agt resolver — no authentication or API keys required.

Flow 4: Agent-to-Agent Discovery

Future capability. The envisioned flow:

  1. An orchestrator agent needs a specific capability (e.g., web scraping).
  2. Queries the .agt registry for agents with capability web-scraping.
  3. Resolves manifests, compares pricing and reputation.
  4. Selects scraper.agt, connects via MCP endpoint.
  5. Delegates the task and receives the result.

Flow 5: Explore Agents

The agent directory at /explore:

  1. User visits /explore.
  2. Page fetches manifests from a seed domain list via /api/agents.
  3. Agent cards are displayed in a grid.
  4. User filters by protocol (MCP, A2A) or capability (research, chat).
  5. User searches by name or description.