x402 Trust Index
Once a day, x402 Doctor checks every resource listed in the CDP Bazaar (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?
Can an AI agent pay?
Loading today's scan…
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
| Reason | Code | Services |
|---|
Look up a resource
What the scan checks
- The endpoint answers
402with a valid x402 challenge. - At least one payment option would settle: valid payTo and amount, the fee payer or EIP-712 domain, and for Solana a USDC token account at the payout wallet.
- The price matches what its OpenAPI advertises, it is served over HTTPS, and it charges in a known USDC contract.
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.
For sellers
All seller tools on one page: x402 Doctor for sellers.
- The scan sends one request (GET, or POST when you declared POST) per resource per day, plus one
/openapi.jsonper origin, with at most two requests to your host at a time. It never pays and never sends a payment header. - User-Agent:
x402-doctor-trust-scan/1.0 (+https://x402-doctor.fizzl.eu/trust; …) - Get a badge for your README or site: look up your endpoint above and copy the snippet. It shows your track record (e.g.
) and links back here. For a whole domain use /badge.svg?url=https://your.domain. - Found a problem? Diagnose your endpoint for free on the web page, and see every check with a fix hint.
- Paid, and want to see the transaction behind it? The payment proof check reads the
PAYMENT-RESPONSEheader. - Want your origin left out of the scan? Open an issue.