Agent Exchange x402 census and directory · census of 2026-10-01 · findings.json · CSV · llms.txt

28,827 listed x402 resources on 2,738 hosts: 67.7% answer a valid 402 today

On 2026-10-01 this host fetched every resource listed in the two public x402 catalogs (Coinbase's CDP Bazaar and PayAI's) plus our own, with an unpaid HEAD then GET. A listing is verified live only when the unpaid GET answered HTTP 402 with a usable accepts list. 6,631 of 9,793 probed resources did (67.7%); 2,403 (24.5%) were gone, unreachable or erroring; the rest hide the 402 behind a POST body, authentication or bot protection, or serve without any challenge.

Since the census, the hourly re-probe has checked 1,050 resources in 7 runs and found 987 verdict changes (list, feed); last run 2026-10-01 06:13 UTC.

What a live 402 looks like today (6,631 resources)

Catalog overlap and how much of each catalog is live

"Listed" counts resources after de-duplication by URL and method; the two catalogs report 19,731 and 11,006 rows respectively. A resource is in "both" when the same URL and method appear in each.

By network

Prices (USDC on Base, 23,920 resources)

Median $0.01, quartiles $0.003 to $0.02, 90th percentile $0.06; 11,580 resources under one cent, 437 at one dollar or more. Most common price points: $0 (13), $1.00 (154), $2.00 (32), $3.00 (20), $4.00 (3), $5.00 (38).

Top sellers by settled USDC volume

From public USDC settlements on Base (EIP-3009 transfers) to each host's payTo addresses, as seen in the outbound history of the 1,570 wallets analysed on 2026-09-30; a floor, not the market. "Sampler share" is the share of payments from wallets that pay dozens of sellers in bursts (monitors and indexers), not customers.

Top sellers by distinct paying wallets

1,569 hosts have two or more distinct payers on record; 13 hosts with settlement history are now dead. All sellers: /sellers.

Dead listings

2,403 resources (24.5% of probed) on 14 hosts answered nothing usable: gone 1,237, unreachable 1,166. Whole hosts dead: agentshelf.syntexa.ch (1,182), x402.asrai.me (318), x402.aurelianflo.com (178), ostland.halowerk.com (125), suedland.halowerk.com (125), mitteleuropa.halowerk.com (125), atlantikland.halowerk.com (125), baltikum.halowerk.com (125), nordland.halowerk.com (125), glim.sh (24), sat.ipintel.ai (3), api.exa.ai (2). Full list: /dead.

Discovery files on seller hosts (492 hosts checked)

Method

CDP Bazaar (api.cdp.coinbase.com/platform/v2/x402/discovery/resources) and PayAI (facilitator.payai.network/discovery/resources) walked completely with limit=1000; plus store.agentexchange.work/.well-known/x402 and /directory and the eight census hosts' /.well-known/x402 and /listings.json. one record per URL and HTTP method; id = first 12 hex of sha1(url) (sha1('METHOD url') when one URL is listed under two methods). every resource once: HEAD then GET with no payment header, user agent agentexchange-bazaar/1.0 (+https://network.agentexchange.work), 8 s timeout, at most 2 requests per second per host, 14 in flight; after 3 consecutive connection errors or 8 consecutive timeouts the host's remaining resources are recorded as unreachable without further requests (counted as probed and dead). Valid 402: the unpaid GET answered HTTP 402 and the JSON body or the PAYMENT-REQUIRED header carried a non-empty accepts list. Dead: connection error or timeout, 404/410, or a 5xx to the unpaid GET. Not verified: everything else: 405/400 on POST-only routes (the 402 sits behind the declared method), 401/403/429, 200 without a challenge, redirects. Prices: USD = atomic USDC amount / 1e6 for USDC assets on Base, Base Sepolia and Solana; other assets have no USD price here. On-chain: payTo addresses joined to ../x402-research/sellers-2026-09-30.json (x402-shaped USDC settlements (transferWithAuthorization / receiveWithAuthorization / Multicall3 batches) in the outbound history (<=500 newest) of every wallet that paid our store since 2026-06-01); sellers never paid by those wallets stay unresolved. one snapshot per resource on the build date; the hourly cron re-probes a rotating slice of 150 and records verdict changes. A "templated" URL (with :param or {param}) is probed as listed, so its verdict says whether the template itself answers; 18.5% do.

Why this index exists

The catalogs list what sellers registered; nobody publishes whether those routes still answer, what their 402 looks like, whether the advertised price is the live price, or whether anyone ever paid. This host measures exactly that, neutrally, for every listed resource, and republishes it as pages, JSON, CSV, an Atom feed of verdict changes, sitemaps and an MCP server, so agents and crawlers can read it without an account. Nothing is sold on the measurement itself; the only paid things are position (featured placement), an on-demand re-probe and an on-demand seller report, all paid per call in USDC with x402 and labelled where they appear.

Machine access

bazaar.json (compact list of every resource, CORS open, cached 1 h) · bazaar.csv · findings.json · sellers-index.json · /r/<id>.json · /seller/<host>.json · /search.json?q= · changes.xml · live.json · MCP (Streamable HTTP, tools find_resources, check_seller, resource) · openapi.json · agent card · x402 manifest · sitemap index · llms.txt. Licence CC BY 4.0.

Questions

What does "valid 402" mean here?

The resource's URL, fetched with an unpaid GET and no payment header, answered HTTP 402 and the JSON body or the PAYMENT-REQUIRED header carried a non-empty accepts list with a payment requirement in it.

Why are POST-only routes not counted as live?

The census probes with HEAD then GET only and never posts a body. A route that answers 405 or 400 to GET is marked method-gated: the 402 may well be there behind the declared method, but an unpaid GET could not see it.

Where do the on-chain numbers come from?

Public USDC transfers on Base (EIP-3009 transferWithAuthorization and receiveWithAuthorization, Multicall3 batches) to each resource's payTo address, joined from a 2026-09-30 analysis of the outbound history of the wallets that had paid our own store. Sellers those wallets never paid stay unresolved; the numbers are a floor.

Does paying for a placement change a verdict?

No. Featured placement buys position on the report and search pages for 30 days and is labelled; verdicts, prices and on-chain facts come from the probe and the chain only.

How often is this updated?

The full census is rebuilt from the catalogs on the build date shown; every hour a rotating slice of 150 resources is re-probed and any verdict change is listed on /changes and in the Atom feed.