How many x402 paid endpoints actually have anyone paying them?

Almost none. The Coinbase CDP Bazaar (the public x402 discovery catalog) contains many thousands of paid endpoints, but only a few percent cross the ≥5-unique-payer threshold in the last 30 days, and demand-side measurement (x402-list.com over 423 instrumented services) shows the top ten services account for ~97.9% of settled USDC volume. Listing is not demand. Payment discovery is nearly universal on x402; paid demand is highly concentrated. See the live cohort ladder on this page for the current-day cut.

← Home · Data hub · Bazaar market map · Report 07 (long-form)

Canonical live answer · refreshed daily

How many x402 endpoints are actually used?

Snapshot as of 2026-08-29T09:01:06Z · every figure below computed from that same snapshot on each build, so the numbers here and on /x402-bazaar-market-map cannot drift.

Short answer: almost none. As of 2026-08-29T09:01:06Z, 642 of 14,536 (4.42%) paid endpoints in Coinbase's public CDP Bazaar report ≥5 unique payers in the last 30 days. Payment discovery is nearly universal; paid demand is highly concentrated. Independent demand-side measurement (x402-list.com over 423 instrumented services, frozen 2026-08-15) reports the top ten services capture ~97.9% of settled USDC volume. Listing is not demand.

The cohort ladder (live snapshot)

Payer thresholds applied verbatim from the snapshot. Denominator is the full indexed endpoint total — not a subset — so the percentages read as “share of the catalog,” not “share of endpoints with any usage data.” The strict thresholds shrink fast because most endpoints have never been paid.

Cohort (last 30 days)	Endpoints	Share of catalog
≥1 unique payer (30d)	14,465	99.5%
≥5 unique payers (30d)	642	4.42%
≥10 unique payers (30d)	236	1.62%
≥100 unique payers (30d)	31	0.213%

Catalog snapshot fetched 2026-08-29T09:01:06Z from https://api.cdp.coinbase.com/platform/v2/x402/discovery/resources.

Two independent measurements, same shape

Two operators, two methodologies, two sides of the market — each finds the same shape: a large listing surface with a tiny paying cohort.

Supply side (this page). On-Chain Agent Intel's daily snapshot of every paid endpoint in Coinbase's public CDP Bazaar, cut against CDP's own quality.l30DaysUniquePayers field. Predicate: ≥5 unique payers in the last 30 days per endpoint.
Demand side (x402-list.com traction dataset). x402-list.com instruments 423 x402 services and publishes a data.traction block over a trailing 30-day window. Frozen 2026-08-15: $206,753 USDC settled, 5,473,120 settlements, 5,745 unique buyers; top-10 services capture ~97.9% of settled volume; the largest single service captures ~83.3%; one buyer inside it settled ~98.7% of that service's volume.

Full whole-catalog write-up in Report 07; the reconciliation across both operators is at the x402 concentration reconciliation.

Method

Catalog source. Coinbase's public CDP Bazaar discovery API at https://api.cdp.coinbase.com/platform/v2/x402/discovery/resources. Every paid endpoint gated behind a 402 that routes through the CDP facilitator ends up auto-indexed there. Each entry carries a quality.l30DaysUniquePayers field — the number of distinct wallets that have paid it in the last 30 days. CDP's own count, not something we compute; using it as the trust filter costs nothing and cannot be self-reported around.

Cohort ladder. For each threshold N ∈ {1, 5, 10, 100}, the endpoint count where quality.l30DaysUniquePayers ≥ N. Endpoints with a missing or non-numeric payer count are excluded from every threshold (they cannot have crossed one). Codified in onchainagentintel-site/build_seo_pages.py::_bazaar_payer_thresholds — the same function powers Report 07 and the live market map, so this page cannot report a different number.

Cadence. The snapshot refreshes via a systemd timer on the indexer host; the site rebuilds daily and picks up whatever snapshot is current at that time.

Limitations

Catalog rotation. Endpoints get added and dropped daily. The shape (large listing surface, tiny paid cohort at the top) is stable across snapshots; the exact counts move slightly from build to build. The number on this page is always the same snapshot the live market map currently serves.
CDP's field is self-facilitated. The 30-day payer count reflects what the CDP facilitator observed. An endpoint that runs its own x402 facilitator and settles direct (like ours — see the Report 06 note on self-facilitated 402) will report a lower CDP-side payer count than its true 30-day total. This is a floor, not a ceiling.
x402-list.com is a sample, not the whole demand side. Their 423 measured services have self-reported coverage of ~17.5% of measured x402 economy volume; the top-1 service instrumentation was explicit (top_1_service_imported=true). Concentration directionally matches our supply-side cut but is not identical by construction.

Cite this answer

Scoped claim sentence. Scope: paid endpoints in Coinbase's public CDP Bazaar discovery catalog (https://api.cdp.coinbase.com/platform/v2/x402/discovery/resources), cut against CDP's own quality.l30DaysUniquePayers field; refreshed on the daily build cadence. As of 2026-08-29T09:01:06Z, 642 of 14,536 indexed paid endpoints (4.42%) report ≥5 unique payers in the last 30 days.

License. Answer prose and every rendered number published under CC BY 4.0 — free to reuse, including in commercial work, provided you attribute “On-Chain Agent Intel” and link back to https://onchainagentintel.io/how-many-x402-endpoints-are-actually-used.

Machine-readable source. The same catalog snapshot backs the live /x402-bazaar-market-map.json export and the CSV export. Suitable for citation and re-hosting under CC BY 4.0.

Also useful: Live market map · Report 07 (long-form) · Concentration reconciliation · How many agents? · All datasets