list-
list-
Grade one x402 route's Bazaar discovery metadata. Returns the diagnosis only: both x402 SDK validator verdicts, the schema-quality score, itemized defects with severities (hollow output schemas, over-500-char descriptions, wrong asset addresses, failed validation), and a 0-100 grade. Use this when you operate an x402 route and want to know exactly what is broken before paying for the repair.
Live
Last successful check: 26 Oct 2026, 08:41 UTC.
- answered, last 24 hours
- 100%
- answered, last 30 days
- 100%
2 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
- 0x097f9685d1e0752bf8b02d61e5ce9be7ea0fba7fnamed by x402 Bazaar
- Listed since
Payments
- different wallets paid it, last 30 days
- 2
- paid calls, last 30 days
- 4
- last paid call (UTC)
As the x402 Bazaar reports, from payments Coinbase's facilitator settled. Read . addrbook has not counted these payments itself.
How it asks to be paid
| Network | Price | Paid in | Settled by | Pays to |
|---|---|---|---|---|
| Base | $0.10 | USDC | Per request | 0x097f9685d1e0752bf8b02d61e5ce9be7ea0fba7f |
From its own 402 answer at UTC. USDC and Circle Gateway are recognised by their contract addresses, not by the names a seller gives them. How payments are read
Checks by endpoint
| Host | Protocol | State | Last checked (UTC) | Last answered (UTC) | 24 hours | 30 days | Tools |
|---|---|---|---|---|---|---|---|
| list- | x402 | Live | 100% | 100% | — |
Also listed as
Other entries that share an endpoint with this one.