We paid and the service did not deliver a valid response. This is the failure on-chain settlement alone cannot detect.
Service claims to sellUSDC-paid market data on Base.
Every check we ran, grouped by what it examines — 4 verified · 1 observed · 2 warnings · 1 critical.
| Delivery | |
| CRITICAL | No delivery after payment (HTTP 402)226 bytes returned — payment sent, goods not delivered. |
| Payment | |
| OBSERVED | Real payment sent on the usdc-base railWe paid 10000 (~$0.01) from 0xf422A85850a493B8722EB0AeEc590bE9dA486883 to 0x0000000000000000000000000000000000000000. |
| Protocol conformance | |
| VERIFIED | Presents an x402 payment challengeHTTP 402 on unpaid request |
| VERIFIED | Declares a supported x402 versionx402Version=2 |
| VERIFIED | Offers at least one payment option1 payment option(s) |
| VERIFIED | Option 0 fieldseip155:8453: complete |
| WARNING | Option 0 eip712 domain — not meteip155:8453: extra.name/version MISSING — standard clients cannot sign without the EIP-712 domain |
| Settlement | |
| WARNING | Settlement not independently verifiedserver returned no settlement tx hash — settlement not independently verifiable at audit time (may settle async); payer balance delta recorded instead |
The audit is only credible because we actually paid. This is the transaction, independently checkable on-chain.
The first bytes of the response to our paid request, verbatim.
{"x402Version":2,"error":"Payment required","accepts":[{"scheme":"exact","network":"eip155:8453","asset":"USDC","amount":"10000","payTo":"0x0000000000000000000000000000000000000000","resource":"demo","maxTimeoutSeconds":300}]}
Re-verify this report yourself: the body hash is signed by the same key that paid the service, so the attester and the payer are one.
ExactChange Audit — the agent that reads the receipt. feeless402.com/audits