The x402 directory of APIs that AI agents pay per request, over x402.
Method
How we measure this905 measured, 17.0% share
Read at . Concentration and coverage computed at . Source: Settlement statistics JSON; measurement methodology.
- listed services measured
- 905
- share of facilitator settlement
- 17.0%
- top 10 services
- 95.4%
- largest single service
- 70.1%
- distinct buyers, 30d
- 11,129
- settlements, 30d
- 1,840,501
A measured floor across 905 listed services on Base, Solana, Celo over the last 30 days, not an ecosystem total. USDC settlements via measured facilitators only, counted net per address: in each transaction every listed address counts what it received minus what it passed on to other listed addresses, self-payments excluded, commissions paid to listed addresses stay in; never summed from per-service figures.
The settlement volume above is 17.0% of the settlement we measure across every facilitator snapshot we hold, enabled or not, over the same 30 days: $1,924,943, a sum per facilitator, not deduplicated. That wider figure is settlement to anyone, not only to listed services; per facilitator it is on Facilitators.
Concentrated: the top 10 services account for 95.4% of that settlement volume (as of 2026-10-28 11:42 UTC).
The single largest service, an imported listing, is 70.1% of that settlement volume, and one buyer is 98.6% of that service's volume.
Over the same 30 days: 11,129 distinct on-chain buyers and 1,840,501 settlements.
Uptime and delisting1,162 up, 103 off, 143 delisted
x402 List is an independent x402 directory of services and APIs that accept x402 payments. We track endpoint pricing, monitored health and observed settlement activity. The figures below describe listed services and the networks we measure; they are not a total for the entire x402 ecosystem.
Directory snapshot
Read at . Counts and health can be cached for 30 seconds; settlement totals for five minutes. Latest monitoring check: . This is the read time, not the observation time of every metric.
| Metric | Value | Window and coverage |
|---|---|---|
| Services | 1,265 | Current listed catalog; excludes services offline for 30 days or more. |
| Endpoints | 9,644 | Current active endpoints of listed services. |
| Average uptime | 92.1% | Mean of each listed service's latest daily UTC rollup. |
| Networks | 36 | Mainnet networks with current pricing on active endpoints of listed services; testnets excluded. |
Source: Directory statistics JSON. Measurement methodology explains the monitored population and the limits of these figures. See current service status or services ranked by measured criteria.
Read at . The 30-day uptime mean covers listed services and may be cached for one minute. Statistics JSON provides current counts; State of x402 reports the 30-day uptime mean.
- answering now
- 1,162
- offline
- 103
- delisted, offline 30d+
- 143
- payment-ready
- 1,195
- uptime 30d, listed
- 97.8%
Of 1,265 listed services, 1,162 are answering now and 103 are offline. A further 143 have been offline for 30 days or more: they are delisted and are not among the 1,265.
Listed services only: 1,265 services, 1,195 payment-ready, uptime over the last 30 days 97.8%.
Want the dated, citable slice we measure? See the State of x402 dataset, or read the x402 basics, how AI agents pay with x402 and the ecosystem blog.
MCP server
Run the MCP server locally:
npx -y x402-list-mcpOr connect your MCP client to the remote server:
https://mcp.x402-list.com/mcpFacilitators
Compare on-chain settlement volume, chain coverage and settler evidence. Volume measures activity, not service quality. Browse x402 facilitators or read the facilitator JSON data.
How an agent uses it
The example endpoint and payment header are placeholders. Use the URL and payment terms returned by your chosen service. In x402 v2, decode the payment terms from the PAYMENT-REQUIRED response header; in v1, read them from the JSON response body. Settlement details arrive in PAYMENT-RESPONSE for v2 or X-PAYMENT-RESPONSE for v1.
curl -i https://api.example.com/dataRetry with a signed payment payload using the header for the service's x402 version.
x402 v2:
curl -H "PAYMENT-SIGNATURE: ..." https://api.example.com/datax402 v1:
curl -H "X-PAYMENT: ..." https://api.example.com/dataServices agents are paying
Read at . Service measurements JSON; measurement methodology.
| Service | Vol 30d | From |
|---|---|---|
| dTelecom x402 Gateway | $36,591.70 | --- |
| Cluster Protocol | $14,210.96 | $0.0005 |
| AX1 Console | $9,920.76 | $0.02 |
| X Pay | $9,690.36 | $0.005 |
| Clash of Coins Checkout | $3,436.79 | $0.001 |
How an agent uses it
- 1
Discover
Fetch the live directory as JSON. Filter by network, category, or price range.
- 2
Call
Hit any listed endpoint. Unpaid requests return HTTP 402 with payment terms.
- 3
Pay and retry
Sign a payment authorization, then retry with the PAYMENT-SIGNATURE header for x402 v2 or X-PAYMENT for v1.
curl https://x402-list.com/api/v1/services?ref=docs | jqSponsor · This spot is open · 28 USDC/week(?)A sponsor supports this site. Learn about sponsorship.
Services agents are paying
Five examples with on-chain volume in the last 30 days, leaving out services labeled Concentrated volume. Not a ranking. Bars on a log scale, one rule per tenfold.
For agents
Everything on this site is also machine-readable.