AI Product Index / The machine-payable web

The machine-payable web

Every endpoint in the x402 Bazaar that an agent can pay for and call: 14,661 of them across 1,527 hosts, with prices, and — the part nobody else publishes — whether they still answer.

Mirrored from Coinbase CDP x402 Bazaar on 2026-08-01, liveness probed 2026-08-01. Raw: stats.json · catalog.json · health.json.

14,661
endpoints
1,527
distinct hosts
$0.01
median price/call
97.2%
answering, last probe

What a call costs

percentileprice per call
cheapest$0.0001
median (p50)$0.01
p90$0.15
most expensive$10000.00

14,635 endpoints publish a price in an asset whose decimals are known. The other 26 are listed without one — guessing six decimals would print a number wrong by orders of magnitude, so they are excluded from price filters rather than sorted as free.

Search it

Queries run against /api/x402/search, the same endpoint an agent would call. Nothing is stored.

Results appear here. With JavaScript off, call /api/x402/search?q=… directly — it returns JSON.

The 25 largest operators

Concentration is the thing the headline count hides: 14,661 endpoints across 1,527 hosts means the typical operator publishes a handful, and a few publish thousands.

#hostendpoints
1 clonecho.builda.company 993
2 agent402.tools 526
3 api.x402node.dev 449
4 x402.forgemesh.io 415
5 oracles-production.up.railway.app 369
6 api.agentstools.dev 300
7 x402.glassnode.com 297
8 api.24klabs.ai 253
9 proxy.suverse.io 189
10 www.stratalize.com 188
11 api.relaystation.ai 158
12 blockrun.ai 149
13 x402-services-production.up.railway.app 147
14 x402.openwebninja.com 145
15 2s.io 141
16 library.forgemesh.io 141
17 agents.x402stock.xyz 132
18 402.com.tr 126
19 gateway.apiosk.com 124
20 api.socialfetch.dev 103
21 eltociear-tokenguard.hf.space 100
22 netintel.dev 100
23 x402-factory.com 98
24 api.strale.io 92
25 data.greeneris.io 91

Provenance and removal

This is a mirror of a public registry, republished so it can be queried and so its liveness is knowable. It states no facts of its own about these endpoints beyond whether they answered a request. If you operate one of them and want it gone, open an issue on the repo — no justification needed, and it is removed on the next build.