How do I get my paid API listed in the x402 Bazaar and facilitator discovery indexes?
Short answer: You don't submit it — you settle through it. We probed about 20 x402 facilitators on October 2, 2026 and found only 4 running a working discovery index: thirdweb (33,352 resources), Coinbase's CDP Bazaar (24,335), PayAI (12,402), and Ultravioleta DAO (1,712). No facilitator exposes a listing API — POST /discovery/resources returned 405/404 on both CDP and PayAI — and each index is independent: a payment settled through CDP lists you on CDP only.
The standard advice ("submit your resource to the Bazaar") describes an endpoint that does not exist. The real sequence is: declare discovery metadata in your 402 response, settle one real payment through each facilitator whose index you want to appear in, then verify the listing per index. And keep the honest second half in view: listing is not demand — an independent crawl counted 31,620 CDP resources on October 13, 2026, and 77% of them had two payers or fewer in 30 days.
The survey, dated
| Facilitator | Discovery index (live probe, Oct 2, 2026) | Resources counted | How a resource gets in |
|---|---|---|---|
| thirdweb | Working index | 33,352 | Payment-triggered cataloging |
| Coinbase CDP Bazaar | Working index — api.cdp.coinbase.com/platform/v2/x402/discovery/resources | 24,335 | Settle a payment through CDP carrying the bazaar discovery declaration |
| PayAI | Working index — facilitator.payai.network/discovery/resources | 12,402 | Settle a payment through PayAI carrying the discovery declaration |
| Ultravioleta DAO | Working index | 1,712 | Payment-triggered cataloging |
| ~16 other facilitators probed | No working discovery index found | — | Payments settle; nothing is cataloged for agents to find |
Counts are dated probes, not live tickers — indexes grow and churn daily. The structural findings are the durable part: 4 of ~20, no listing API anywhere, no shared catalog.
Quotable: “ScriptMasterLabs' October 2, 2026 survey: only 4 of about 20 x402 facilitators run a working discovery index (thirdweb 33,352 resources; CDP Bazaar 24,335; PayAI 12,402; Ultravioleta DAO 1,712). No facilitator offers a listing API — listing is triggered only by a settled payment through that facilitator, and each index is independent.”
Re-probed live tonight (October 14, 2026)
| Probe | Result |
|---|---|
GET CDP /discovery/resources | Live — returned current mainnet resources (Base USDC, x402 v2, bazaar extensions present); the feed's pagination total tonight reads 37,267 resources, up from 24,335 in the October 2 survey |
POST PayAI /discovery/resources | 404 tonight, verbatim: "No resource is served at POST /discovery/resources" — the October 2 no-listing-API finding re-verified live |
GET PayAI /discovery/resources | Live — returned current resources; the newest entry's lastUpdated was timestamped minutes before this probe |
GET PayAI bare /discovery | 404 — the index lives at /discovery/resources, not the bare path; wrong-path queries read as "no index" if you stop there |
| GET thirdweb guessed discovery path | 404 on the path we tried — thirdweb's index exists (counted Oct 2) but is not at the conventional facilitator path; verify against its own docs before concluding anything |
| SML's own surface | SqueezeOS manifest still declares discoverable:true with the CDP facilitator; Verdict Protocol agent.json still reports LIVE_SETTLEMENT_VERIFIED (POST /decide $0.25, POST /seal $0.01, Base, x402 v2) — the settlement-first posture this page describes is the one we run |
Why the indexes don't merge — and why it matters
Each facilitator catalogs only the payments it processes. There is no federation step, no cross-posting, and no listing API to shortcut it. A seller who settles exclusively through CDP is invisible to an agent shopping PayAI's index, and vice versa. Discovery in x402 is therefore not one marketplace — it is (as of the last full survey) four separate shelves, and a seller's real distribution work is settling a genuine first payment on each shelf they care about.
The second consequence is quieter: because the listing trigger is a settled payment, most listings' first — and often only — payer is the seller's own test payment. The independent October 13, 2026 crawl of the full CDP index (31,620 resources, 2,280 hosts) found 45.8% of resources had exactly one payer in 30 days and 77% had two or fewer. That crawl is another author's work, cited here as corroboration, not as our measurement — but it matches what the payment-triggered mechanism predicts: supply lists itself; buyers are the scarce side.
Where the decision gate sits in this
Discovery answers what can an agent find? It never answers should the agent pay for it? A catalog entry carries a price, a network, and a payTo — no judgment about whether this call, at this price, from this provider, is worth firing. That prior question is the decision gate's job: score the payment before signature (≥0.80 auto-pay, 0.50–0.79 confirm, <0.50 escalate to a human), seal the decision as a receipt, and only then settle — through whichever facilitator's shelf the purchase belongs on. SML's Verdict Protocol is that layer, and its own launch is the worked example: the gate held while the first facilitator under it failed at settle and was swapped the same day (the full log is in our facilitator settle-reliability field test). Being listed gets an agent to your door; the gate is what a careful buyer runs before knocking.
Claim Receipts
- Survey counts (thirdweb 33,352; CDP Bazaar 24,335; PayAI 12,402; Ultravioleta DAO 1,712), the 4-of-~20 finding, the POST /discovery/resources 405/404 results on CDP and PayAI, and the per-index independence finding: ScriptMasterLabs' facilitator discovery survey, live probes, October 2, 2026 (
x402-telemetry-build/facilitator-survey.md). - Tonight's re-probes (CDP discovery live with pagination total 37,267; PayAI discovery live with a minutes-old lastUpdated; PayAI bare /discovery 404; PayAI POST /discovery/resources 404 tonight; thirdweb guessed path 404): direct probes run October 14, 2026, ~20:20 EDT.
- CDP index size on October 13, 2026 (31,620 resources, 2,280 hosts; 45.8% one payer, 77% two or fewer in 30 days): independent author's full-index crawl published on dev.to, October 13, 2026 — external corroboration, labeled as such, not an SML measurement.
- SML surface checks (SqueezeOS manifest discoverable:true + CDP facilitator; Verdict Protocol agent.json LIVE_SETTLEMENT_VERIFIED, /decide $0.25 USDC, /seal $0.01 USDC, Base, x402 v2): live checks, October 14, 2026.
- Gate bands (auto_act ≥0.80, advisory 0.50–0.79, escalate <0.50; decider local-heuristic-v1, calibrated=false): live check of
scriptmasterlabs.com/api/harness/status, October 14, 2026.
Relevant SML products
- Verdict Protocol — the decision layer a buyer runs before paying any discovered resource: /decide $0.25 USDC, /seal $0.01 USDC, Base, x402 v2, LIVE_SETTLEMENT_VERIFIED.
- Decision-Gated Machine Payments — the pattern: a confidence score gates whether a machine payment fires (≥0.80 auto-pay, 0.50–0.79 confirm, <0.50 escalate), before any facilitator or index is involved.
- Which x402 Facilitator Actually Settles Reliably? — the companion field test: the same signed payloads, failed by one facilitator, settled by another in ~1 second.
- Provider Trust — verify the counterparty before the payment; a catalog listing is a claim, not a verification.
- 402Proof Solana rail — SML's own standard x402 v2 facilitator now also settles on Solana mainnet (native USDC, exact scheme): flat 0.005 USDC facilitator fee per settlement paid in-transaction, settlement-proven 2026-11-02 (SELF-PROOF canaries, including fee-carrying tx 5d6b2ojznZ6p3BQ52eEAGayj6KQAoJxZSosSNggQGM9SRx1GqL2Gq4McWCCxVUiPjMFef24p5vJ6eP7zTfKrodXg).
- What Is the x402 Payment Protocol — the rail itself: 402 challenge, signed payload, verify, settle, catalog.
All five URLs returned HTTP 200 on October 14, 2026, before linking.
Do it yourself: get listed, per index
- Declare discovery metadata in your 402 response. Carry the bazaar discovery declaration (method, input/output shape, service metadata) so a facilitator can catalog the resource from the payment flow. No declaration, no listing — even if the payment settles.
- Settle one real payment per facilitator. Pick the indexes you want (tonight: CDP and PayAI verified live; thirdweb and Ultravioleta counted in the Oct 2 survey) and settle a genuine first payment through each. One facilitator's settlement does not list you anywhere else.
- Verify per index, by query. GET each facilitator's
/discovery/resourcesand find your resource. "Listed" is a per-index fact you can check, not a status a dashboard grants. - Don't mistake the listing for traction. Your first payer will probably be you. Track unique payers and settled calls in the index's quality fields over 30 days — that, not presence, is distribution.
- Make the buyer's gate pass easy. Stable pricing, a live 402 challenge an agent can probe for free, and a verifiable settlement history are what a decision gate (and the human behind it) can actually score. Discovery gets you found; receipts get you paid.
Honest caveats
- The 4-of-~20 survey and its resource counts are dated October 2, 2026 probes. Counts drift daily (CDP alone grew from 24,335 in our survey to 31,620 in the independent October 13 crawl), and a facilitator counted as index-less in the survey could have shipped one since. Tonight's re-probe re-verified CDP and PayAI live; it was not a full 20-facilitator re-survey, and we do not present it as one.
- The thirdweb index was counted via its own surface in the survey; the conventional-path GET we tried tonight 404'd. That is a statement about the path, not about thirdweb's index existing.
- The payer-distribution figures (45.8% / 77%) are an independent author's crawl of the CDP index, cited with attribution — SML did not re-crawl 31,620 resources tonight and does not claim those numbers as its own.
- Owner proof-wallet settlements referenced via the Verdict Protocol launch are self-tests, labeled as such everywhere — never customer purchases.
Update — November 3, 2026: we built the other side of this
When this survey ran, ScriptMasterLabs rented shelf space like everyone else — settle through CDP, appear on CDP. On November 2, 2026, both of our own facilitators began publishing their own /discovery/resources indexes, per the x402 spec's federated discovery model, with no Coinbase involvement:
- OMNIGATE (Base and Arc) — discovery index: 129 resources at the November 3, 2026 probe.
- 402Proof (XRPL, Xahau, Solana) — sidecar discovery index: 14 resources — 13 XRPL partner resources plus one catalogued from live post-launch traffic.
What changes for a seller: settle through our facilitators and the resource is catalogued in our indexes under the same settlement-as-listing rule this page documents — except the shelf is ours. Facilitator fees: OMNIGATE 0.005 USDC flat per settlement on Base and Arc, from the first settlement, no free allowance; 402Proof 0.01 in the invoice’s asset per XRPL invoice settlement, 0.005 USDC flat on Solana, 0.01 XAH flat on Xahau for third-party settlements. What does not change: nobody cross-posts you (our 177 strict rows inside CDP’s Bazaar, out of 107,465 resources, came from CDP settlements, separately), presence is still not demand, and listings still rot — Ultravioleta DAO held 55 SML rows on October 24, 2026 and zero on November 3, which is why the probe now runs daily and publishes itself: x402 Index Health. The follow-up: We went from asking to be listed to running the index.