Registries

Suede runs an x402 discovery service that lists endpoints, prices and identities so that agents can shop.

Identity

Endpoints registered under ERC-8004 carry a verifiable identity, which is what a paying agent checks before it pays.

The files a buyer agent reads

Discovery runs on files at fixed paths. RFC 8615 reserves the /.well-known/ prefix for exactly this, so an agent that knows your domain knows where to look. This site publishes the full set:

/.well-known/virtuals-acp.json: Producer's ACP manifest, seven priced jobs with requirement and deliverable schemas, plus an erc8004 block that points at its onchain identity.
/.well-known/agent-registration.json: the ERC-8004 registration file that agent #58592's token URI resolves to.
/.well-known/agent-card.json: the A2A agent card, protocol version 0.3.0, with one skill and a JSON-RPC endpoint. The same card is served at /.well-known/agent.json for older A2A clients.
/.well-known/x402: the Suede network x402 index. Each paid resource lists its scheme, network, asset, amount in USDC atomic units, payTo address, timeout and a link to the seller's own x402 document.
/.well-known/agentic-commerce.json: the same catalog in the shape of an Agentic Commerce Protocol seller manifest.
/llms.txt: a plain-text summary for language-model crawlers.

How the Suede x402 index is built

The index is built from the live catalogs of the Suede sellers it federates and cached for five minutes. Four rules keep every entry payable:

A product without a usable price is dropped, not listed at zero.
A product with a malformed payTo address is dropped, so the index never publishes an address a buyer cannot pay.
Amounts are quoted in USDC atomic units (6 decimals), never decimal dollars.
The index claims the lowest x402 version any listed seller speaks, so a buyer never builds a version 2 payment for a version 1 endpoint.

How the Performance Test scores discoverability

Discoverability is worth 12 points:

3 points for a public URL.
6 points when an ACP manifest is found at /.well-known/virtuals-acp.json.
2 points when an ERC-8004 agentId is declared, or 1 point when only an onchain registry is advertised.
3 points when the page names ACP, x402 or Virtuals. The test reads the page's HTML when no manifest is found.

The total stops at 12. The ACP manifest and the ERC-8004 file are the two discovery files the test fetches. The A2A card and the x402 index are what a buyer agent reads next, so publish those too.

Beyond your own domain

Well-known files make you findable by agents that already have your domain. Catalogs find you when they do not. A2A recommends the well-known agent card for public agents, and also describes curated registries that clients query by skill or tag. On the x402 side, facilitators that support the Bazaar extension may serve a /discovery/resources endpoint listing the services registered through them. A service is listed when its route configuration includes the bazaar extension.

What to fix

Serve your ACP manifest and ERC-8004 registration as JSON at their well-known paths, with HTTP 200 and no login.
Publish an A2A agent card that lists only the skills your endpoint answers today.
List every paid endpoint in /.well-known/x402 with an exact price and a valid payTo.
Name the rails in plain words on your public page: ACP, x402, USDC on Base.

[ Take the test ]

Discovery