nimapro1381/x402-service-index

x402 Service Index

A free, daily-refreshed snapshot of live x402 pay-per-call API services discovered across the public Coinbase CDP bazaar and PayAI discovery feeds, each one live-probed with one unpaid request per crawl so alive reflects a real answer, not a directory listing.

• —400 services tracked, 395 alive as of the latest crawl (generated_at field in index.json).
• —Fields: resource, method, network, price_usd, alive. network is a CAIP-2 chain id (e.g. eip155:8453 = Base).
• —This is deliberately a thin summary — resource URL, HTTP method, network, advertised price, and the alive flag, nothing else. It does not include descriptions, input/output schemas, pay_to addresses, asset contracts, latency, or uptime history.

Operator disclosure

Quietforge compiles this index and also operates some of the endpoints in it — every row whose resource host is qf-api.quietforge-studio.workers.dev. Read this dataset knowing that. The thin schema published here has no source column, so the host string is how you identify them; the full paid records label them source: quietforge.

Row order is not in our favour. Rows are sorted by CDP 30-day call count, then 30-day payers, then whether the endpoint answered our last probe, then upstream freshness. Who operates a row is never a sort term. Don't take that on trust — filter on the host string above and see where our rows land in any snapshot. Before 2026-09-22 they sorted first, because the crawler used the operator as its first sort key; that was undisclosed self-preferencing and has been removed.

We are also held to the same per-host cap. The crawl keeps at most a fixed number of endpoints per host so no single operator floods the index. Until 2026-09-22 our own host was exempt from that cap and held 16 slots while every third party was held to 3; the exemption is gone, and the crawl now refuses to write an index in which our own host exceeds the cap.

Why this exists

x402 lets an AI agent pay for an API call with on-chain USDC and no signup/KYC, but there is no single, verified index of who is actually live. Aggregator listing pages get stale fast (dead tunnels, services that never answer 402 correctly, price drift). This snapshot is generated by re-probing every listed service on a schedule, so alive is measured, not asserted.

Full records (paid)

Untruncated descriptions, input/output schemas, pay_to addresses, asset contracts, parsed live-402 challenge prices, TLS result, 30-day call/payer counts, and per-probe uptime history are served by our own x402 pay-per-call API — no account, no signup, no API key, paid in USDC on Base:

• —GET https://qf-api.quietforge-studio.workers.dev/v1/x402/services — filterable list ($0.005)
• —GET https://qf-api.quietforge-studio.workers.dev/v1/x402/services/{id} — one record + uptime history ($0.002)

Manifest: `https://qf-api.quietforge-studio.workers.dev/.well-known/x402.json`

Source & refresh

• —Live, sortable version of this table: quietforge-studio.pages.dev/x402-index/
• —Raw JSON: quietforge-studio.pages.dev/x402-index/index.json

License & delisting

CC BY 4.0 — attribute "Quietforge Studio x402 Service Index". Data is aggregated from public discovery APIs; probing is ours. We are not affiliated with any listed service other than our own (see the operator disclosure above) and do not vouch for any of them — alive: true only means the endpoint answered a probe. If you operate a listed service and want it removed, email quietforgestudio@agentmail.to and it will be delisted within one crawl cycle.

See also

• —x402 Market Pulse — the companion time series: how much USDC actually settles per 24 h to the seller addresses in this index, measured from Base Transfer logs (aggregate-only; the per-seller view is the paid /v1/x402/demand route).

Files

• —index.json — snapshot with metadata (generated_at, attribution, count, alive_count, services[]).
• —index.csv — flat table of the services[] array for quick loading with pandas/datasets.