x402 Merchant Audit
api.
Is this merchant safe to depend on? Audits up to ten x402 endpoints in one call and returns a verdict — ready, partially ready or not ready — with the specific blockers. Checks each endpoint serves a payable challenge with well-formed terms and a declared input schema, and adds the cross-endpoint check no single probe can make: whether every endpoint pays the same recipient. Never pays anything.
Live
Last successful check: 26 Oct 2026, 07:33 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
- 0x25e8245f07d5e4873987293dad666afbe56a9608named by x402 Bazaar
- Listed since
Payments
- different wallets paid it, last 30 days
- 2
- paid calls, last 30 days
- 2
- 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.025 | USDC | Per request | 0x25e8245f07d5e4873987293dad666afbe56a9608 |
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 |
|---|---|---|---|---|---|---|---|
| api. | x402 | Live | 100% | 100% | — |
Also listed as
Other entries that share an endpoint with this one.