x402 Trust Index

Once a day, x402 Doctor checks every resource listed in the CDP Bazaar, Circle's Agent Marketplace, GoPlausible's discovery list, the XRPL AI Hub and nohumans.directory's catalogue (CC BY 4.0) and PayAPI Market (x402) and in the MPP directory (Stripe + Tempo) the way a paying agent would, and stops at the 402 challenge. Would a payment settle today, and how often did it over the last 30 days?

What the numbers show: x402 health report, October 2026 (payable share, seller concentration, networks, prices and the most common seller mistakes). Other ways to check an endpoint: x402 endpoint checkers compared. The whole index as an open dataset: x402 Trust Index on Hugging Face (CC BY 4.0, updated daily).

Can an AI agent pay?

In the scan of 31 Oct 2026, an agent could pay 97% of the 42,320 paid services checked (x402 and MPP) without a failed payment. One seller has 10,162 of them (24%); without it, an agent could pay 96% of the other 32,158.

Paid and delivered?

Loading the latest spot-buy…

Reading the 402 shows that a payment would settle, not what comes back for it. So every Sunday x402 Doctor buys a random sample of up to 30 endpoints that are "go" here (one per seller, at most $0.05 each, x402 in USDC on Base, from a dedicated wallet), sends the example input the seller declares in its listing, and measures on-chain whether money left the wallet. A small sample: read it as a signal, not a score. Data: /api/trust/spot · every run.

What goes wrong

Reasons in the latest scan. A service can have more than one; "works, with warnings" services count here too.

Show as a table
ReasonCodeServices

What is behind the endpoints

Sellers with the most endpoints
SellerEndpointsDistinct services

A seller often lists the same API many times (once per coin, city or ticker). Payable endpoints of one seller with nearly the same description count as one service; the kind of service is judged by TypeSafe Jev (a keyword guess until Jev has seen it).

Possible bait

Loading…

Look up a resource

What the scan checks

Agents get this track record in every pre-payment check (GET /api/v1/preflight, $0.001): a seller that was payable on fewer than half of its scanned days gets a caution.

Questions

How many paid x402 endpoints are there?

In the scan of 31 Oct 2026, x402 Doctor checked 42,320 paid API endpoints (41,901 x402 and 419 MPP) listed in the CDP Bazaar, Circle's Agent Marketplace, the MPP directory and other public indexes. The 41,167 payable ones are 26,976 distinct services from 2,449 sellers: a seller often lists the same API once per coin, city or ticker.

What share of x402 endpoints can an AI agent actually pay?

97% in the scan of 31 Oct 2026: 41,167 of 42,320 endpoints would take a payment without failing (38,595 as listed, 2,572 with a warning). One seller has 10,162 of them (24%); without it, an agent could pay 96% of the other 32,158. The most common problems: only Circle Gateway options, paid from a Gateway balance and not by standard x402 clients (1,683); doesn't ask for payment at all (offline or broken) (661); charges for a different address than the one called (357).

On which networks can AI agents pay x402 endpoints?

Endpoints payable per network in the scan of 31 Oct 2026: Base 40,199, Solana 11,738, Polygon 9,383, Arbitrum 8,322, Arc 4,393, World Chain 3,804. Most endpoints offer more than one network. Every endpoint per network, payable or not and why: x402-doctor.fizzl.eu/stellar, /algorand, /xrpl and /xlayer.

Where can I get this data?

Free, without an API key: GET https://x402-doctor.fizzl.eu/api/trust?url=<endpoint> for one endpoint's 30-day record, GET /api/trust/summary for the totals, and the whole index as an open dataset on Hugging Face (huggingface.co/datasets/x402Fizzl/x402-trust-index, CC BY 4.0, updated daily). Before paying an endpoint, an agent can ask GET /api/v1/preflight?url=<endpoint> for go, caution or no_go ($0.001).

For sellers

All seller tools on one page: x402 Doctor for sellers.

by · all tools and live demos at fizzl.eu