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: 15,392 of them across 1,993 hosts, with prices, and — the part nobody else publishes — whether they still answer.

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

15,392
endpoints
1,993
distinct hosts
$0.01
median price/call
99.3%
answering, last probe

What a call costs

percentileprice per call
cheapest$0.0010
median (p50)$0.01
p90$0.10
most expensive$1000.00

15,352 endpoints publish a price in an asset whose decimals are known. The other 40 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: 15,392 endpoints across 1,993 hosts means the typical operator publishes a handful, and a few publish thousands.

#hostendpoints
1 intel.rallylive.ca 820
2 agent402.tools 599
3 api.x402node.dev 356
4 api.agentstools.dev 342
5 api.delx.ai 240
6 x402-factory.com 202
7 402.com.tr 161
8 fittings.sh 145
9 api.strale.io 144
10 agents.x402stock.xyz 138
11 atlantikland.halowerk.com 125
12 baltikum.halowerk.com 125
13 mitteleuropa.halowerk.com 125
14 nordland.halowerk.com 125
15 ostland.halowerk.com 125
16 suedland.halowerk.com 125
17 netintel.dev 124
18 x402.orthogonal.com 123
19 api.particle.pro 100
20 crawlspur.halowerk.com 100
21 minia2a.uk 100
22 tempo.halowerk.com 100
23 agentpaystore.com 94
24 data.greeneris.io 91
25 api.locus.report 90

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.