Guides · List your service

How do I list my service in an agent catalog?

By serving a paid endpoint and letting the catalog index it. This guide walks that path step by step, checked against the catalog’s own documentation and live API on 2026-09-02. It also says plainly what a listing gets you — and what it does not.

What does a listing actually get you?

A listing gets you discoverability. AI agents and their operators can find your service, read its price, and build a valid call — once indexed, your entry is served through the catalog’s public APIs, its MCP server, and the surfaces built on them. A listing does not get you revenue. Those are different things, and mixing them up is how sellers end up disappointed.

Some listed services receive real, publicly visible payments. Many listings have never been paid at all. That split is measurable, and it moves — so read it live instead of here: see which sellers show verified revenue, browse the directory’s verified and listed-only split, and watch the live market.

The FAQ answers “Can I make money selling to agents?” in four sentences. This page is the long version it promised.

Why does the x402 Bazaar get the walkthrough?

Because it can be checked. The x402 Bazaar is Coinbase’s public catalog of x402 services, and its discovery and validation endpoints are open — no account, no API key. Every step below was verified against its live documentation and its live API on 2026-09-02. It is also a data source this site reads, for the same reason.

It is not the only catalog. The x402 specification repository points to community-maintained directories, and the x402.org facilitator keeps its own catalog, separate from the Bazaar. Other payment rails run their own discovery surfaces; the protocol pages describe each rail without ranking them. No catalog pays for coverage here, and a listing anywhere earns no badge on this site — verification does.

What do you need before you start?

• A service that does one job, priced per call. x402 quotes a price per request — a micropayment model, not a subscription. Agents buy single calls.
• A public HTTPS URL. The catalog only indexes endpoints it can reach over HTTPS; private and tunneled setups fail its checks or rank poorly.
• An address to receive payment. The x402 payments this site verifies settle in USDC on the Base network, so your listing names the on-chain address that receives them — publicly, as the buyer-side checks expect.
• Coinbase Developer Platform credentials. Listing runs through the CDP Facilitator — the service that verifies and settles each payment — and connecting your server to it takes CDP API keys. Reading the catalog needs no key; settling payments does.

How does a service get into the catalog?

There is no listing form. The Bazaar’s documentation says it directly: “There is no registration form or separate API call.” You serve a paying endpoint the standard x402 way, prove it works, and the catalog indexes it after its first settled payment. Four steps, as documented on 2026-09-02:

Step 1 — Serve your route behind a 402

When a request arrives without payment, your service answers with HTTP status 402 — “Payment Required” — naming its price, network, and token. The x402 server libraries handle this. With the TypeScript CDP SDK, createX402Server also declares catalog metadata for every route automatically; in Python, discovery is opt-in and you declare it per route.

Step 2 — Write metadata an agent can act on

An agent reading your listing has to know when to call you and how. The documentation asks for a plain description of when to use the endpoint, input and output schemas, and realistic examples — without them, agents can find your endpoint but cannot construct a valid call. Keep the description under 500 characters; the facilitator rejects longer ones.

OTTO, our example agent, buys text extraction at $0.01 per page. The listing OTTO’s operator acts on has exactly this shape: one line saying what the endpoint extracts and when to use it, the $0.01-per-page price, and a schema naming the input. Nothing in it is marketing. All of it is instructions.

Step 3 — Validate the endpoint

The Bazaar publishes a validation endpoint, open to anyone with no API key. Send it your URL and method; it checks that the endpoint is reachable, answers with a 402, and serves a metadata block the catalog would accept for indexing. Fix what it flags before spending anything.

Step 4 — Complete one real, settled payment

The first successful paid call through the CDP Facilitator is what triggers indexing. Pay your own endpoint once — a real payment, with real settlement — and the catalog picks the route up from it. That settled payment, not a form, is the registration.

How do you stay listed?

By staying paid and staying up. The catalog’s published rule as of 2026-09-02: a resource that goes 30 days without a settlement is removed from both the catalog and its search results. An endpoint that stops answering 402 is eventually removed from the index entirely.

That rule is the honest economics of listing in one sentence: a listing does not bring revenue — it requires revenue to keep existing.

Ranking inside the catalog weighs real usage and listing quality over a rolling 30-day window, recomputed on a six-hour schedule, and new endpoints rank conservatively until usage accrues. Placeholder descriptions score zero on metadata quality. Endpoints on shared tunneling domains are weighted below dedicated domains.

Above plain indexing sits a hand-curated featured tier. Its requirements are published — live mainnet payments, measured availability, health probes, complete metadata — and the selection itself is editorial. Meeting the bar qualifies an endpoint for review; it does not guarantee a slot.

What will buyers check about you?

The same things this site tells them to check. The buyer-side list — one stable published address, a payment history with real payer spread, a quote that matches the listed price, claims that point at public records — is on how to evaluate a seller. Set your service up so every one of those checks passes cheaply. An on-chain seller does not get to tell its own story; the ledger tells it.

And do not manufacture history. Self-dealing payment patterns — dust, wash trading, listing farms — are exactly what buyer-side checks and this site’s verification filter for.

Where are the primary sources?

• Read “Get discovered (Bazaar)” — the Coinbase Developer Platform page behind every step here: the checklist, metadata rules, validation, delisting, and curation.
• Read the Bazaar discovery documentation — the public read side, usable without an API key.
• Read the x402 specification repository — the payment flow itself, and the ecosystem’s list of community-maintained directories.