Why list here
- Agents and buyers search one catalog instead of hunting for your URL.
- Discovery metadata tells them what your endpoint does, what it costs, and how to call it before they pay.
- A successful settled payment through the CDP Facilitator is what triggers indexing after validation.
What you need to do
- Deploy the route on public HTTPS and return 402 with discovery metadata when unpaid.
- Optionally validate with CDP’s validate endpoint before you rely on indexing.
- For routes with inputs, add accurate schemas and examples so agents can construct valid calls.
- Follow the metadata content policy—descriptive text only, not instructions to agents.
- Complete a successful paid call through the CDP Facilitator to get indexed.
Highlighting Request
Request
Wallet, agent, or app that selects an offer and signs payment.
GET
GET
Sells access and publishes payment requirements.
GET
Verifies signatures and submits chain transactions on behalf of merchants.
402
Return 402 with discovery metadata when the call is unpaid.
Wallet, agent, or app that selects an offer and signs payment.
Discovery metadata describes the endpoint, the price, and how to call it.
Discovery metadata describes the endpoint, the price, and how to call it.
Discovery metadata describes the endpoint, the price, and how to call it.
Discovery metadata describes the endpoint, the price, and how to call it.
Discovery metadata describes the endpoint, the price, and how to call it.
Discovery metadata describes the endpoint, the price, and how to call it.
Discovery metadata describes the endpoint, the price, and how to call it.
Discovery metadata describes the endpoint, the price, and how to call it.
{ "x402Version": 2 }Discovery metadata describes the endpoint, the price, and how to call it.
Discovery metadata describes the endpoint, the price, and how to call it.
Sells access and publishes payment requirements.
Discovery metadata describes the endpoint, the price, and how to call it.
Verifies signatures and submits chain transactions on behalf of merchants.
Pay and retry
Wallet, agent, or app that selects an offer and signs payment.
PAYMENT-SIGNATURE
PAYMENT-SIGNATURE
Sells access and publishes payment requirements.
PAYMENT-SIGNATURE
Verifies signatures and submits chain transactions on behalf of merchants.
Verify
Wallet, agent, or app that selects an offer and signs payment.
Sells access and publishes payment requirements.
verify
verify
Verifies signatures and submits chain transactions on behalf of merchants.
verify
Settle
A successful settled payment through the CDP Facilitator triggers indexing.
Wallet, agent, or app that selects an offer and signs payment.
Sells access and publishes payment requirements.
Indexing follows a settled payment through the CDP Facilitator.
Indexing follows a settled payment through the CDP Facilitator.
Indexing follows a settled payment through the CDP Facilitator.
Indexing follows a settled payment through the CDP Facilitator.
Indexing follows a settled payment through the CDP Facilitator.
Verifies signatures and submits chain transactions on behalf of merchants.
Indexing follows a settled payment through the CDP Facilitator.
Response
Wallet, agent, or app that selects an offer and signs payment.
200
200
Sells access and publishes payment requirements.
200
Verifies signatures and submits chain transactions on behalf of merchants.
TypeScript vs Python
TypeScript sellers using the CDP SDK get automatic Bazaar wiring for each concrete HTTP route. Python sellers opt in per route and declare discovery metadata themselves—there is no equivalent auto-generated declaration.
After you are listed
Ranking uses real usage and listing quality over a rolling window; curation is a separate, editorial featured tier for high-quality mainnet endpoints. Resources without settlement for 30 days are removed from the catalog, and listed resources are re-screened against the content policy.
CDP documentation
For engineers
Discovery metadata lives in the extensions.bazaar block on payment-required responses. TypeScript createX402Server adds a minimal declaration per METHOD /path route; enrich routes with declareDiscoveryExtension from @x402/extensions/bazaar. Python uses declare_discovery_extension and registers the Bazaar resource-server extension explicitly.
POST https://api.cdp.coinbase.com/platform/v2/x402/validate checks reachability, 402, a valid bazaar block, and facilitator indexing requirements (no API key). On verify/settle, the CDP Facilitator can return an EXTENSION-RESPONSES header with bazaar status success, processing, or rejected. Indexing after a settled payment can take up to 15 minutes.
The x402.org facilitator maintains a separate catalog; it is not the CDP Bazaar.
