agentutility / docs

How it works.

Three routes in. Pick the one that matches your agent harness. Every route hits the same set of endpoints, settled in USDC on Base via the x402 protocol.

§ I · The protocol

x402, in one paragraph.

POST to any endpoint. If the request lacks payment, the server returns HTTP 402 Payment Required with a structured body describing exactly what to pay, where, and how. Sign a USDC transferWithAuthorization for that amount, attach the signed payment as an X-PAYMENT header, and retry. The facilitator settles on-chain and the response comes back in the same request lifecycle.

# 1. unpaid request
curl -X POST https://x402.org/v1/secrets-exposure-check \
  -H "Content-Type: application/json" \
  -d '{"repo":"vercel/next.js"}'

# response: 402 with payment requirements
{
  "x402Version": 1,
  "accepts": [{
    "scheme": "exact",
    "network": "base",
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "maxAmountRequired": "20000",  // 0.02 USDC, 6 decimals
    "payTo": "0x8f5cb67b49555e614892b7233cfddebfb746e531"
  }]
}

# 2. sign, retry with X-PAYMENT header
curl -X POST https://x402.org/v1/secrets-exposure-check \
  -H "X-PAYMENT: $SIGNED_AUTHORIZATION" ...

§ II · MCP

One install. Every endpoint.

For coding agents (Claude Code, Cursor, Codex, Replit Agent), the MCP server handles x402 settlement so your agent just calls tools by name. The server discovers every endpoint at startup; new clusters show up automatically.

# Claude Code
claude mcp add x402 --command "npx x402-deployer-mcp"

# Cursor / Codex / Replit
# add to mcp.json:
{
  "mcpServers": {
    "x402": { "command": "npx", "args": ["x402-deployer-mcp"] }
  }
}

§ III · Discovery

ERC-8004 agent card.

agentutility's portfolio is registered on the ERC-8004 Identity Registry on Base as agentId 47167. Agents that resolve the agent's URI get the full agent card with every endpoint enumerated and priced. Pure on-chain discovery — no DNS, no signup.

# resolve via our own agent-card endpoint
curl -X POST https://x402.org/v1/agent-card-resolve \
  -H "Content-Type: application/json" \
  -d '{"agent_id":47167}'

# → owner address, agent_uri, full card JSON

See the live card at /agent-card.

§ IV · Catalog

Machine-readable registry.

The full registry is served as JSON at /registry.json. Filter by cluster with ?cluster=prooflayer.

curl https://agentutility.ai/registry.json?cluster=edge-market