Tabular Contract Audit
api.
Audit your own delimited data against a contract you declare, and get one pass/fail plus the exact row and clause of every breach. Checks types, required values, enums, numeric bounds, lengths, patterns, uniqueness, composite primary keys, null-rate ceilings, header drift and encoding damage in one pass. A pass means the audit was complete and nothing broke, so a file beyond the bounds reports incomplete rather than passing. Nothing is fetched: you supply the rows.
Live
Last successful check: 26 Oct 2026, 07:33 UTC.
- answered, last 24 hours
- 100%
- answered, last 30 days
- 100%
1 wallet 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
- 1
- paid calls, last 30 days
- 1
- 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.12 | 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.