Machine commerce · full catalogue census · 18 November 2026

35,149 endpoints. 71 sellers with real demand.

Every x402 directory shows the supply. This is the demand side: one complete pass over the public catalogue, every resource, every host, and the directory's own 30-day call and payer counts. The result is uncomfortable: 90.4 % of listed endpoints have fewer than ten calls a month, and the top ten resources take 70.2 % of all calls.

35,149listed resources on 3,255 hosts
2.45 Mreported calls in 30 days
90.4 %of endpoints get fewer than 10 calls
71hosts with sustained, multi-payer demand

Source: the public x402 discovery endpoint, one pass, 18 November 2026. Calls and payers are the directory's own reported figures, not settled revenue. Payer counts are summed per resource, not deduplicated. Download the sample.

Demand is not spread across the catalogue. It is concentrated in a handful of hosts.

54.7 % top 1 resource 15.5 % ranks 2–10 20.0 % ranks 11–100 9.8 % the other 35,049
The single largest host reports 1.34 M calls with 1,294 payer counts. Excluding it, the entire catalogue reports 1.11 M calls in 30 days. A call is not a sale: it can be a 402 challenge, a health check or a self-call.

The sustained-demand list

What a real seller looks like

A host qualifies when the directory reports at least 100 payer counts, at least 50 calls, and at least 2 calls per payer in 30 days. That is a deliberately low bar for diversification, and only 71 hosts clear it. Hosts with a single call per payer look like faucets, giveaways or self-tests, not repeat demand.

HostPayers 30dCalls 30dCalls/payerEndpoints
keyring-agent.blockchhub.link7,42027,0783.653
www.api-xpay.com1,601231,286144.4615
agent-data-tools.revmesh2074.workers.dev1,3194,8403.67739
console.ax1.vc1,2941,336,1331,032.561
blockrun.ai1,21888,08772.32171
agent402.tools1,17813,60111.55625
api.x402node.dev9522,3332.45303
api.loyalspark.online8812,3302.6479
api.nansen.ai6094,0366.6338
x402.orthogonal.com5736,58111.49308

The list includes consoles, gateways and data providers; it is a demand signal, not an endorsement. Delivery probes (live 402, price match, latency, schema) are the next layer and are sold as an audit.

What this changes

Three conclusions for anyone building on x402

1. Another endpoint is not a strategy. With 35k listings and about 150 hosts showing meaningful payer counts, supply is free. Placement, trust and delivery are scarce.

2. The buyer side is being built now. Buyer-controlled payment clients, escrow and refunds, and quote verification all need one input: which seller is real, and what did it deliver last time. That input is not for sale anywhere as a neutral dataset.

3. MCP paid demand is still tiny. 550 MCP resources in the catalogue report 738 calls in total, a median of one. The rail is being laid (MPP, AP2, ACP); the paying demand is not there yet. Build for it, but do not budget on it in 2026.

Buy the verified detail

Three ways to use the census

Verified Demand Feed

$299 / month

  • Full 35k-row census, daily
  • All 71 sustained-demand hosts
  • Day-over-day deltas and history
  • CSV + JSON by email
Request access

Seller Audit

$499 one-off

  • 402 correctness and Base USDC price match
  • Latency p50/p95 and 7-day uptime
  • Schema and delivery receipt checks
  • Public badge if it passes
Book an audit

The Real 71

$99 / month

  • Weekly one-page brief
  • New entrants, dropouts, price moves
  • Demand by category
  • Free headline, paid detail
Subscribe

B2B invoices in USDC on Base; self-serve data through x402 on request. No card processor, no custodian.

Method and limits

How the number was produced

Source. The public x402 discovery endpoint (api.cdp.coinbase.com/platform/v2/x402/discovery/resources), all pages, 1,000 rows per page, one pass on 18 November 2026. The run is reproducible with scripts/bazaar-census.ts in the GTXAgent repository.
Deduplication. Resources are deduplicated by exact URL; hosts are the lower-cased hostname. A host is not a legal entity and can front several sellers.
What the call count is. The directory's reported 30-day call count. It is not settled revenue and not unique buyers. Payer counts are summed across resources, so the 96,457 total is an upper bound, not a unique-wallet count.
What the list is not. It is not a delivery guarantee. A host can report demand and still fail a live request. Delivery probes, price matching and schema checks are the paid audit.
Corrections. If you operate a host on this page and the figures are wrong, write to [email protected] with the resource URL and the evidence; the census is versioned and corrections are published.

Download the sample JSON See the paid endpoints