Agent Registry Lookup
Default/gateway/api/agents/registry/lookup
- Exact token, entity, and route metadata for agents
- Highly structured and cheap enough for frequent reads
- Best first purchase for registry validation loops
Resource catalog
This page is the machine-friendly index for the gateway. It describes what each route returns, how it should be priced, and what kind of buyer is likely to use it.
The default paid entry points are Registry Lookup, Network Status / Verification, and Docs / Knowledge Excerpts. Everything else expands the catalog once the core payment loop is working.
These are the first three routes agents should try by default: a registry lookup for exact metadata, a Base verification check for live state, and a premium docs excerpt for compact answers.
/gateway/api/agents/registry/lookup
/gateway/api/agents/network/status
/gateway/api/agents/docs/excerpts
/gateway/api/agents/scope/quote
/gateway/api/agents/workflows/execute
The paid flow should be visible on the catalog page so crawlers can connect the route, the price, and the retry mechanism in one pass.
Read the catalog entry and manifest to see the exact endpoint, product name, and price.
Call the endpoint once without payment to receive the x402 quote and settlement details named by the manifest.
Settle in the quoted settlement asset, then keep the payment proof or reference for the next request.
Retry the same request with x-alumni-payment and receive the protected payload.
These are specialized resources we should surface next so the catalog feels deep instead of narrow.
/gateway/api/agents/contracts/metadata
/gateway/api/agents/token/normalize
/gateway/api/agents/wallet/balance
/gateway/api/agents/wallet/holders
/gateway/api/agents/tx/explain
These are the first specialized products that should feel paid because they reduce labor or remove ambiguity.
/gateway/api/agents/deployments/verify
/gateway/api/agents/routes/health
/gateway/api/agents/chain/gas
/gateway/api/agents/address/risk
/gateway/api/agents/abi/summary
These are higher-value products that combine retrieval, reasoning, and packaged outcomes into a stronger purchase.
/gateway/api/agents/docs/answer
/gateway/api/agents/launch/readiness
/gateway/api/agents/integration/plan
/gateway/api/agents/incidents/triage
/gateway/api/agents/evidence/pack
These routes give agents something they already need every day: current market prices, comparisons, triggers, and recurring watchlists.
/gateway/api/markets/crypto/snapshot
/gateway/api/markets/metals/snapshot
/gateway/api/markets/cross-asset/comparison
/gateway/api/markets/threshold/alerts
/gateway/api/markets/watchlist/starter
/gateway/api/markets/watchlist/monitor
/gateway/api/markets/volatility/summary
/gateway/api/markets/conversion/quote
Keep the responses short, explicit, and structured so a client can act on them without human interpretation. The demo page should show this contract in motion.
Public pages can describe the resource, but paid routes should answer with the price, the accepted asset, and the next request the client should make.
Prefer predictable field names, consistent status codes, and compact payloads that can be cached or replayed by an agent client.