x402 Doctor
x402-
Why is my x402 endpoint broken? Diagnose and debug an x402 payment endpoint (or MCP server) when payments fail: checks the 402 challenge, accepts[] (network, payTo, amount, asset), resource URL, Solana settlement readiness, which wallets and agents can pay, Bazaar/OpenAPI discovery and the browser paywall. Returns every check with a fix hint. Read-only: never pays. Bulk: 1000 credits for $0.80 via /api/v1/credits.
Live
Last successful check: 26 Oct 2026, 05:57 UTC.
- answered, last 24 hours
- 100%
- answered, last 30 days
- 100%
5 different wallets paid it in the last 30 days, as the x402 Bazaar reports. Payments
How addrbook checks →Connect
https:x402: an unpaid request gets a 402 with the price and pay-to wallet. addrbook never pays.
Who's behind it
- Listed by
- x402 Bazaarlast seen UTC
- Wallets named
- 0x6b0f4651ed42893ab58139938175e4a69f175f25named by x402 Bazaar
- Listed since
Payments
- different wallets paid it, last 30 days
- 5
- paid calls, last 30 days
- 6
- last paid call (UTC)
As the x402 Bazaar reports, from payments Coinbase's facilitator settled. Read . addrbook has not counted these payments itself.
Its x402 endpoints have not listed a payment option addrbook could read yet.
Checks by endpoint
| Host | Protocol | State | Last checked (UTC) | Last answered (UTC) | 24 hours | 30 days | Tools |
|---|---|---|---|---|---|---|---|
| x402- | x402 | Live | 100% | 100% | — |
Also listed as
Other entries that share an endpoint with this one.