Verdict 402
verdict.
Did a model reply leak what it should keep secret? Canary tokens and secret phrases searched by code (even split, spaced or uppercased), then paraphrases of the system prompt read by the engine. Returns clean, review or leak.
Live
Last successful check: 26 Oct 2026, 07:19 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
- 0xb36c56a749f81ffeb44a134082dd4744e1d254ebnamed by x402 Bazaar
- Listed since
Payments
- different wallets paid it, last 30 days
- 2
- paid calls, last 30 days
- 5
- 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.009 | USDC | Per request | 0xb36c56a749f81ffeb44a134082dd4744e1d254eb |
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 |
|---|---|---|---|---|---|---|---|
| verdict. | x402 | Live | 100% | 100% | — |
Also listed as
Other entries that share an endpoint with this one.