AISkills402:
api.
x402 Listing Review: Catalogs, Scanners, Buyers — Reviews how a paid HTTP resource sold over x402 is advertised to catalogs, scanners and buyer agents, and how the seller's own scripts read those catalogs back, from pasted 402 bodies, OpenAPI documents, discovery files, liveness guard code, catalog presence check scripts and buyer alerts. Flags a tiered tariff advertised as one row (a comparison bot reads the structured amount, not the description), one liveness clock for several catalog rows t…
Live
Last successful check: 26 Oct 2026, 07:12 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
- 0x8e37022edcf0f21cf3c9f93fee9d4d32519f36f4named 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.05 | USDC | Per request | 0x8e37022edcf0f21cf3c9f93fee9d4d32519f36f4 |
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.