Why your x402 endpoint isn't in the CDP Bazaar (and how to fix it)
Your x402 endpoint returns a 402, takes payment, and works. But it isn't in the CDP Bazaar, so agents searching the catalog never find it. Below is every cause we know of, with the symptom and the fix for each. You can work through it by hand for free.
extensions.bazaar declaration, and the settle request carries both paymentPayload.extensions.bazaar and paymentPayload.resource. CDP then probes the route with the example input from your declaration and expects a 402. So you need a well-formed challenge on a public https URL, CDP as the facilitator, and at least one settled payment that carries the metadata.- No payment has settled through CDP yet
- Payments settle through a different facilitator
- extensions.bazaar is missing or malformed
- extensions sits inside accepts instead of next to it
- The description is too long
- resource.url says http:// behind a proxy
- The resource field is missing
- The 402 body is empty or accepts is malformed
- A POST route is described as GET
- External $ref/$id in a schema, or paymentPayload.resource not sent
- The route uses a bare wildcard
- You changed price or metadata and the listing didn't update
- A bare request or CDP's probe gets a 400 instead of a 402
- Several URLs collapse into one entry
- The route dropped out after 30 days without a settlement
- The 402 body is right but the PAYMENT-REQUIRED header is missing
- resource.url names a different URL than the one requested
- Only Circle Gateway payment options are offered
None of them fit? See accepted as “processing”, never indexed. Listed but not featured? See indexed, but not curated (enriched: false). Listed but hard to find? See how a listing behaves.
x402 endpoint not showing in Bazaar: quick triage
| What you see | Most likely cause |
|---|---|
| Nobody has paid the route yet | 1 |
| Real payments have landed, still not listed | 2, then 3, 4 and 5 |
| Your app runs behind Render, Railway, Fly, Heroku, nginx or a load balancer | 6 |
| A plain request to your route, without its parameters, gets a 400, 409 or 422 | 13 |
Your decoded challenge has extensions inside an accepts entry | 4 |
| Some x402 clients say there are no payment options | 8 |
CDP's validation fails its payment_required_header check | 16 |
CDP's facilitator answered rejected | 3 (read rejectedReason) |
| Valid challenge, settled through CDP, status “processing”, still not listed | 13 and 10, then the open reports |
The decoded challenge's resource.url has a different host or path than the URL you called | 17 |
Every accepts entry has extra.name: "GatewayWalletBatched" | 18 |
| Was listed, now gone | 15 |
| Several of your URLs show up as one entry | 14 |
Listed, but agentic.market shows enriched: false | Not curated |
| Listed, but with the wrong method or no input schema | 9 |
| Listed, but showing an old price or description | 12 |
CDP Bazaar not indexing your route? Ask it directly first
CDP's discovery API is public. Open this in your browser with your receiving wallet address:
https://api.cdp.coinbase.com/platform/v2/x402/discovery/merchant?payTo=0xYOUR_PAY_TO_ADDRESS
If your route shows up there, it's listed. If the list is empty or your route is missing, read on.
Your own server can also read CDP's answer. On verify and settle, CDP's facilitator returns an EXTENSION-RESPONSES header: base64 JSON whose bazaar.status is success (cataloged), processing (accepted, being cataloged) or rejected (with a rejectedReason). No bazaar key means discovery wasn't submitted at all. processing doesn't confirm that indexing will succeed (Coinbase's troubleshooting notes).
1. No payment has settled through CDP yet
Symptom
Your challenge looks right, but the route has never been paid. This is the most common cause for a brand-new endpoint.
Fix
Make one real, paid call to the route that settles through CDP's facilitator. A cent is enough. Then give the Bazaar time to crawl it. It doesn't have to be a mainnet payment: a Coinbase contributor confirmed in cdp-sdk #835 that a testnet settlement through CDP works too, because the Bazaar indexes your live metadata, as long as extensions.bazaar.info.input and paymentPayload.resource are set.
?mode=paid) makes that payment for you, on Base mainnet in USDC, for routes priced up to $0.05. Its result is in settlement_echo. The report's bazaar_index_status check covers this.2. Payments settle through a different facilitator
Symptom
You've had real, settled payments, but the route still isn't listed.
Fix
The CDP Bazaar only learns about routes from settlements that go through CDP's facilitator. A Coinbase contributor confirmed this in cdp-sdk #827: “CDP Bazaar only surfaces resources that settle through the CDP Facilitator.” If your server is set up with another facilitator, CDP never sees those payments. That includes the x402.org facilitator, which keeps its own separate catalog, not the CDP Bazaar. Point the route at CDP's facilitator (it needs a CDP API key), then make one more paid call.
3. extensions.bazaar is missing or malformed
Symptom
Payments settle, but there's nothing for the Bazaar to index. Decode your 402 challenge, and either extensions.bazaar isn't there or it's incomplete.
Fix
Declare discovery metadata on the route. In the Python SDK that's declare_discovery_extension(...) passed as the route's extensions, plus registering bazaar_resource_server_extension on the resource server. At minimum, extensions.bazaar.info.input.type must be "http" or "mcp". If you include info.output, it needs a type too.
Make the example match the schema. Coinbase's docs say rejections are usually strict JSON Schema validation: your declared input must validate against schema.properties.input.
Also check the paying side. The settle request has to carry paymentPayload.extensions.bazaar, so a client that drops the extension when it sends the payment leaves CDP with nothing to index (see x402 #3557).
schema.properties.input, so if CDP's facilitator answers rejected, its rejectedReason is the place to look. The report's bazaar_extension check covers this.4. extensions sits inside accepts instead of next to it
Symptom
Your 402 has a complete Bazaar declaration, but it's inside a payment option, at accepts[0].extensions.bazaar, instead of at the top level of the 402 body. Payments settle and nothing is indexed. It's an easy mistake in hand-rolled 402 responses, and in code ported from x402 v1, where discovery metadata sat inside each payment option as outputSchema.
Fix
Move extensions to the top level of the 402 body, next to accepts, and to the same place in the decoded PAYMENT-REQUIRED header. The x402 v2 specification defines extensions on the 402 response itself, and an accepts entry has no such field. Clients copy the top-level extensions into the payment they send, and the x402 SDK drops an extensions key it finds inside an accepts entry, so CDP never gets your declaration. Then make a new settlement.
accepts[0] and not at the top level. It still checks the block's contents under bazaar_extension, so you also learn whether anything else is wrong with it. The report's extensions_placement check covers this.5. The description is too long
Symptom
Everything else is right, but payments fail. Coinbase's docs say CDP's facilitator rejects verify and settle requests whose description is over 500 characters, and sellers have reported the failure being hard to trace (see x402 #2993).
Fix
Keep the route's description to 500 characters or fewer. One or two sentences is plenty: lead with what the endpoint does, in the words a buyer would search for, then say when an agent should call it (a “Use when ...” sentence).
description_length check covers this.6. resource.url says http:// behind a proxy
Symptom
Your public URL is https://, but the decoded challenge advertises http://. Your host terminates TLS and forwards plain HTTP to your app, so the app builds the URL from what it sees. CDP's validation only accepts https:// resource URLs.
Fix
Tell your server to trust the forwarded scheme. For uvicorn:
uvicorn main:app --proxy-headers --forwarded-allow-ips='*'
# or set the env var
FORWARDED_ALLOW_IPS=*
For other stacks, read X-Forwarded-Proto (Express: app.set("trust proxy", true)), or hardcode your public https base URL.
scheme_mismatch check covers this.7. The resource field is missing
Symptom
The challenge has payment options but no resource, so the Bazaar doesn't know which URL it's cataloging.
Fix
Include resource.url: the full public https URL of the paid route. Current x402 SDKs fill it in for you. Hand-rolled 402 responses often leave it out.
resource_present check covers this.8. The 402 body is empty or accepts is malformed
Symptom
x402 v2 puts the challenge in a base64 PAYMENT-REQUIRED header, and some servers send {} as the body. Clients and crawlers that read the body find no payment options.
Fix
Keep the header, and also return the same decoded JSON as the 402 body. Make sure accepts is a non-empty array of objects, each with scheme, network, asset, amount and payTo.
parse_error.9. A POST route is described as GET
Symptom
Your route takes a JSON body, but the listing (or the validation) treats it as GET, so it sends no body and gets an error instead of a 402.
Fix
Declare the body in the discovery metadata. In the Python SDK, pass body_type="json" plus an example input and input_schema to declare_discovery_extension. Make sure the route key says POST too.
"method": "POST" and a sample "body". Unlisted probes, pays and asks CDP using the route's real method.10. External $ref/$id in a schema, or paymentPayload.resource not sent
Symptom
Payments settle through CDP and CDP's validation says the route would be accepted, but it never appears in the catalog. Sellers in x402 #3045 traced this to two things on their side.
Fix
Inline your schemas. If the input schema or output.schema in your Bazaar declaration has a $ref or $id pointing to an external URL, inline the referenced definitions and drop the external $id. A Coinbase contributor confirmed this cause in cdp-sdk #835, where indexing failed with “schema must not contain external $ref/$id references”. In x402 #3045, a $ref in output.schema broke CDP's validator, and a seller who had fixed output.schema was still unlisted until they did the same for the input schema. CDP's /v2/x402/validate passed their route both times. After the fix and a new settlement, it was indexed.
Send paymentPayload.resource when you settle. Coinbase's docs say the settlement that triggers indexing must set both paymentPayload.extensions.bazaar and paymentPayload.resource, and a maintainer said in x402 #3045 that settlement succeeds without them. Current SDKs fill it in. Hand-rolled settle code often doesn't. One seller found that adding it alone wasn't enough: they also had to settle with an x402 v2 payload, where resource is an object rather than a URL string.
info and schema, input and output) for $ref and $id values that aren't local #/... references, and lists the exact JSON path of each one it finds. It can't see what your server sends CDP when it settles, so it doesn't cover paymentPayload.resource. After you fix either one, the $0.10 Check + real payment (?mode=paid) makes the fresh settlement you need. The report's schema_external_refs check covers this.11. The route uses a bare wildcard
Symptom
The route is declared as /prices/*, so the listing can't tell agents what goes in the path.
Fix
Use a named parameter in the paywall's route pattern, such as GET /prices/:symbol, so the discovery metadata names the path parameter. With the CDP SDK's TypeScript createX402Server, the route key also needs a specific HTTP method: Coinbase's docs say a wildcard method doesn't give the SDK enough to generate discovery metadata.
routeTemplate, the Check flags a bare * segment. The report's route_template check covers this.12. You changed price or metadata and the listing didn't update
Symptom
The route is listed, but with an old price, description or schema (see cdp-sdk #813).
Fix
The Bazaar takes a route's description, tags and price from a settlement through CDP, so a change shows up only after a new payment settles, and can take a while after that. Make a new paid call after the change: a Coinbase contributor said in cdp-sdk #835 that indexing can't be retriggered on an existing settlement. Then check the crawl time again before assuming it's stuck. Ranking is separate: Coinbase's docs say it's recomputed every six hours.
bazaar_index_status result includes when CDP last crawled it, plus 30-day calls and unique payers, and listed_price_match compares the listed price and payment details with your live 402.13. A bare request or CDP's probe gets a 400 instead of a 402
Symptom
A plain request to your route, without its parameters or body, gets a 400, 409 or 422 instead of a 402. Crawlers, discovery tools and agents checking a route before they pay send exactly that kind of request, so they never see your price.
The same thing can stop indexing. A payment settled through CDP and the facilitator said processing, but the route never shows up. After a settlement, the Bazaar probes your route with the example input from extensions.bazaar.info.input, or an empty body if you didn't declare one. If your input validation runs before the x402 middleware, the probe gets a 400, 409 or 422 instead of a 402, and indexing stops there. A Coinbase contributor traced a stuck route to exactly this in cdp-sdk #830: the probe got a 409.
Fix
Let the x402 middleware answer before your input validation runs, so an unpaid request gets a 402 with the payment requirements in the PAYMENT-REQUIRED header whatever its input. If validation has to come first, at least make sure the example input in your declaration passes it and comes back as a 402. Then make a new settlement.
method and body fields for a POST route, to check the rest. The report's probe_response check covers this.14. Several URLs collapse into one entry
Symptom
You serve many resources, such as /data/0xabc…/report and /data/0x123…/report, but the Bazaar lists them as a single entry.
Fix
Coinbase's docs say the Bazaar turns any path segment that is entirely a UUID, an EVM address or transaction hash, or a Solana address or transaction hash into a generic route parameter. To keep resources listed separately, add a prefix or suffix so the segment isn't a bare identifier, such as /user-<uuid> instead of /<uuid>.
15. The route dropped out after 30 days without a settlement
Symptom
Your route was listed, and now it's gone from the catalog and search results.
Fix
Coinbase's docs say resources that go 30 days without a settlement are removed, and endpoints that stop returning a 402 are eventually removed too. A listed route needs ongoing paid traffic through CDP's facilitator. Keep sending paymentPayload.extensions.bazaar and paymentPayload.resource on every settlement: a Coinbase contributor said in cdp-sdk #835 that this keeps your quality metrics aggregating and your route listed.
?mode=paid) can make a settlement for routes priced up to $0.05. The report's bazaar_index_status check covers this.16. The 402 body is right but the PAYMENT-REQUIRED header is missing
Symptom
Your route answers an unpaid request with a 402 and a correct challenge as JSON in the body, but sends no PAYMENT-REQUIRED header. Tools that read the body are happy with it. For x402 v2, though, CDP's validator and the Bazaar indexer read the header, not the body, so CDP's validation fails the route on its payment_required_header check and it can't be listed.
Fix
Send the same JSON, base64-encoded, in a PAYMENT-REQUIRED header, and keep it in the body too (cause 8). Current x402 SDKs set the header for you. Hand-rolled 402 responses often leave it out. Then make a new settlement through CDP.
PAYMENT-REQUIRED header, even when the body is right, and when the header is there but doesn't decode to base64 JSON with payment options in accepts. It skips x402 v1 challenges, which carry the challenge in the body and have no such header. The report's payment_required_header check covers this.17. resource.url names a different URL than the one requested
Symptom
You call https://api.example.com/data, but the decoded challenge says resource.url is another host or path: an internal hostname, localhost, your platform's default domain instead of your own, or a different path. Buyers and catalogs that use resource.url go to the wrong place. In a weekly public x402 health report (Fizzl, week ending Nov 9, 2026), 788 resources named another URL in their 402 than the one requested. Nothing documented says the Bazaar drops a route for this, so Unlisted reports it as a warning.
Fix
Build resource.url from your public origin: the https URL buyers actually call, with the same host and path. Behind a TLS proxy, trust the proxy's forwarded headers so the URL stays https and keeps the public host (see cause 6 for uvicorn and Express), or set your public base URL in config. A trailing slash, a default port, the query string and a route parameter such as :symbol or {symbol} in place of the real value don't count as a mismatch.
resource.url with the URL your 402 was served from, after redirects. The http/https part is cause 6. The report's resource_url_match check covers this.18. Only Circle Gateway payment options are offered
Symptom
Every entry in your challenge's accepts is a Circle Gateway option, marked by extra.name: "GatewayWalletBatched". Gateway options are paid from a Gateway balance that standard x402 clients don't have, so those agents find no option they can pay. Gateway options also use scheme exact, so looking at the scheme name alone won't show this: it's extra.name that marks them. In a weekly public x402 health report (Fizzl, week ending Nov 9, 2026), 1,502 resources offered only Circle Gateway options.
Fix
If standard x402 agents should pay too, add a plain exact option next to the Gateway one: same network and price, with the token's own EIP-712 name and version in extra (for USDC on Base, "USD Coin" and "2") instead of GatewayWalletBatched. Keep the Gateway option for buyers who have a Gateway balance. Circle's docs describe a 402 that lists both as the server “correctly offering both payment methods”.
accepts entry is a standard exact option and at least one is a Circle Gateway option. The report's standard_payment_option check covers this.If none of these fit: accepted as “processing”, never indexed
Symptom
Your challenge is valid, a payment settled through CDP's facilitator, and the facilitator answered with bazaar.status: "processing". CDP's own validation says the route would be accepted. Days later it still isn't in the catalog.
What's known
Coinbase's docs say processing means the metadata was accepted and is being cataloged asynchronously, and that it doesn't confirm indexing will succeed. Routes that do get indexed see it too, so it tells you nothing either way.
Two of the reports have since been answered by a Coinbase contributor, and both turned out to be fixable on the seller's side: cdp-sdk #830 (CDP's probe got a 409, cause 13) and cdp-sdk #835 (an external $id in the schema, cause 10). As of October 4, 2026, x402 #3266 and x402 #3281 are still open with no maintainer answer, and there's no confirmed fix for them.
What to try
Rule out causes 1 to 18 first, especially 13 and 10, since several of them produce the same symptom. Then make one fresh settlement through CDP after your last change: indexing can't be retriggered on an existing settlement, and a testnet settlement works (cause 1). If it's still missing after a few days, add your route and settlement details to one of the open issues above. More reports make it easier for CDP to find the pattern.
bazaar_index_status check tells you whether you're in this state: not indexed, but CDP would accept the route. Paid mode can make a fresh settlement for you. Unlisted can't make CDP index a route, and it won't claim to.Indexed, but not curated (enriched: false)
Symptom
Your route is in the CDP Bazaar, but agentic.market's record for your service shows enriched: false, often with an empty category or description, and you're not in the featured slice. This is a different problem from not being indexed (see cdp-sdk #838).
What it means
A Coinbase contributor explained in #838 that enriched is only turned on for the hand-picked editorial set of curated endpoints. Meeting the published criteria makes an endpoint eligible to be selected, not entitled to it: selection is at Coinbase's discretion, based on service quality, category coverage and ecosystem fit.
Coinbase's curation requirements are: live x402 payments on mainnet, at least 99% availability over 30 days (above 99.5% gets priority), passing the platform health probe, agent-ready metadata (a complete input schema, a description that tells an agent when to use the endpoint, per-call pricing, supported networks and documented error responses), and passing validation. Curated endpoints that fail consecutive health probes are down-ranked, then dropped from the featured tier, and restored once they recover. The docs don't describe an application process.
bazaar.curated, read from CDP's discovery API (the payTo lookup above), which marks curated resources with curated: true and leaves the field out otherwise. It's true or false, or null when Unlisted couldn't tell: the lookup failed, or your route couldn't be matched in the listing. Unlisted doesn't read agentic.market's enriched field, and it can't get a route curated.How a listing behaves once you're in
- Only the first 5 tags count. CDP's facilitator keeps the first 5 valid entries of
resource.tags(1 to 32 printable ASCII characters, no case-insensitive duplicates) and silently drops the rest. Of the 59,927 entries in CDP's public discovery listing on October 25, 2026, none had more than 5 tags. Put your most important tags first. - Description and tags refresh only when a payment settles. Changing them in your 402 doesn't update the listing by itself. The Bazaar takes your metadata from a settlement through CDP's facilitator, so make a new paid call after a change: a Coinbase contributor said in cdp-sdk #835 that indexing can't be retriggered on an existing settlement.
lastCalledAtand call counts have been observed by sellers to lag by hours. Coinbase doesn't document this, but a payment that just settled may not show up in the listing'squalitynumbers yet.- Indexed doesn't mean found in search. Being in the catalog doesn't put you near the top of Bazaar search. Ranking is CDP's, and a description that says what the endpoint does, in the words a buyer would search for, helps.
tag_count warns when you declare more than 5 tags and names the ones that would be dropped. listed_price_match compares your live 402 with your listing and warns when the live price is more than twice the listed one or the payTo, network or asset differ. search_visibility runs Bazaar search for up to 3 phrases from your own description and tags and reports your rank, or “not in top 20”. It's information only. description_screening warns on wording that reads like instructions to an AI agent, such as “ignore previous instructions”. It's a small heuristic of Unlisted's own, not CDP's screening. In paid mode, extension_response reports whether your server passed CDP's EXTENSION-RESPONSES header on to the buyer, and its bazaar status. Most servers don't, and that's normal. Unlisted can't make CDP index or rank a route, and it won't claim to.Check all of it in one call
Unlisted runs every check above against your endpoint and asks CDP for its live index status. No signup and no API key: you pay per call in USDC on Base through x402, and you're only charged if the check completes.
POST https://unlisted.sh/diagnose
Content-Type: application/json
{"url": "https://your-api.example.com/paid-route"}
| Mode | Price | What it does |
|---|---|---|
| Check | $0.02 | Your 402 challenge, the Bazaar declaration, and CDP's live index status |
Check + real payment (?mode=paid) | $0.10 | All of the above, plus one real test payment to your route. Once per domain per 24 hours. |
Replace the sample URL with your own endpoint. The report opens with bazaar.indexed (true, false, or null if CDP couldn't be reached) and bazaar.curated (true, false, or null if unknown), then one result per check with a fix for each failure.