What is the x402 Bazaar, and how do I get my API listed?
Short answer
The Bazaar is x402's discovery layer, a machine-readable catalog of paid endpoints that agents and developers can search. A seller describes its endpoint in a "bazaar" extension inside the 402 reply, and facilitators index it. On Coinbase's facilitator there is no sign-up form. An endpoint is listed after the first paid call to it settles.
What it is
An agent that can pay still has to find something worth paying for. The Bazaar answers "what x402 services exist, and how do I call them?" in a form software can read.
It is not one website. It is an extension to x402 version 2, plus search endpoints that facilitators expose. Each facilitator that supports it has its own catalog of the endpoints it has processed.
How a listing is made
- The seller describes the endpoint. The 402 reply includes
extensions.bazaar, with aninfosection and a JSON schema covering the HTTP method (or MCP tool), the inputs it takes, and an example of the output. - A facilitator indexes it. When the facilitator handles a payment for that endpoint, it records the description.
- Buyers search the catalog through the facilitator's discovery endpoints,
GET /discovery/resourcesandGET /discovery/search.
A facilitator can tell the seller how indexing went through an EXTENSION-RESPONSES header, with a bazaar.status of success, processing or rejected.
Getting listed on Coinbase's catalog
Coinbase's documentation describes the rule plainly: there is no registration form. An endpoint is indexed after the CDP facilitator settles a paid call to it. So:
- Use the CDP facilitator for settlement.
- Include the
bazaarextension in your 402 reply. The server SDKs have a helper for it. - Make one real paid call to the endpoint.
The same documentation says the catalog lists more than 23,000 x402 resources. It is public and needs no API key to search.
Writing a listing that gets used
Agents choose tools by reading descriptions. Make yours specific:
- Say what goes in and what comes out, in one sentence.
- Give a realistic example input and output.
- Name the unit of work the price covers: per search, per page, per thousand rows.
- Describe when not to use it. It saves agents wasted payments and you wasted support.
Other places to be found
The Bazaar is one channel. Independent directories and explorers crawl x402 endpoints too, and some verify listings with real payments. See explorers and discovery in the directory.
It also helps to be found the ordinary way: clear public documentation, an llms.txt file, and an OpenAPI description, so that search engines and AI assistants can read what you offer.
How mature is it?
The x402 documentation describes the Bazaar as in early development. Expect the format and the catalogs to keep changing, and do not rely on one catalog as your only route to customers.
Sources
- Bazaar extension specification
- Bazaar, x402 documentation
- Get discovered, Coinbase CDP documentation
- Bazaar, Coinbase CDP documentation
Facts checked against these sources on . Protocols change, so the official specification wins if it disagrees with this page. Read this page as Markdown.
Related questions
Who writes this. Ask402 is published by Havok Holdings LLC, which also runs Agent402, one of the x402 services covered here. Agent402 is labelled wherever it appears. Everything else is described from each project’s own documentation, and nobody pays to be listed.