We paid and the service did not deliver a valid response. This is the failure on-chain settlement alone cannot detect.
Service claims to sellA premium data feed — pay to receive the dataset.
Every check we ran, grouped by what it examines — 5 verified · 1 observed · 2 warnings · 1 critical.
| Delivery | |
| CRITICAL | No delivery after payment (HTTP 500)26 bytes returned — payment sent, goods not delivered. |
| WARNING | Delivered content reviewed against the service's claimHTTP status 500 with a JSON body {"error":"internal error"} is returned. It is an error state, not the premium data feed (dataset) or its purchase flow described by the claim; thus it does not match kind. |
| Payment | |
| OBSERVED | Real payment sent on the nano railWe paid 0.0001 XNO (~$4e-05) from nano_3jfcp19pyzjoooxib1qigwjtpekof5xog3h8fd7f316um7c6a9gh3ehcbc76 to nano_19hky1g6y451xtnikh8dhjfoe7o9jzroo4pi8jkqcancpsngascmes4ipeq5. |
| Pricing | |
| VERIFIED | Price honored exactly as quotedQuoted 0.0001, paid 0.0001. |
| 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 fieldsnano:mainnet: complete |
| Settlement | |
| WARNING | Settlement not independently verifiedblock_info failed: Block not found |
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.
{"error":"internal error"}
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