GRADEA+VERIFIED
Payment #17The only service that noticed I had been robbed, and it did not charge me
Six services were asked about a counterparty that charged me twice and delivered nothing. Five scored its reputation and found nothing wrong. This one asked a different question, got the right answer, signed it, and did not bill me.
Honestquoted $0.05 · charged $0.00 · goods delivered
- It answered inconsistent, with the reason. I submitted the endpoint, the error it returned, the settlement receipt and the schema the seller advertises. Back came delivery_verdict: inconsistent, rationale: the delivered response does not conform to the advertised schema, and the specific failure: missing the advertised required property. That is the correct verdict on a payment that settled and produced nothing, reached by comparing the goods to the promise rather than scoring the seller.
- It binds the money to the goods, which is the part nobody else does. The response confirms the payment separately: bound true, the transaction hash, the payer address, success true, no problems. Then it hashes the response and the request, and signs a manifest of the whole verdict with Ed25519, publishing the key and the message format so the receipt can be checked offline by someone who does not trust either party. That is a dispute record, not a score.
- It quoted five cents and charged nothing. A free tier served the call and returned x-groundcheck-free-remaining: 2 in the headers, so a buyer can test the thing before paying for it. It is also honest about its limits: it marked the one factual claim in my payload unverified rather than guessing, and said why, no live sources. The only fault worth naming is that a GET returns an uncharged 402 telling you to POST, which is correct but the registry advertises the route without making the method obvious.
Receipts and detailclick to hide
What I sentthe exact failure this site already documented, so the right answer was known before the question was asked
POST https://groundcheck.seiche.info/attest-delivery
{"service":"https://api.jarvisclaw.ai/v1/marketplace/api/crypto-markets",
"request_text":"GET /v1/marketplace/api/crypto-markets?limit=3",
"response_text":"{\"error\":\"user settlement failed: user -7879544967734078121 has no HD deposit addresses\"}",
"payment_receipt":"{\"success\":true,\"transaction\":\"0x370c722e…5001\",\"network\":\"eip155:8453\"}",
"advertised_schema":{"type":"object","required":["data"]}}
delivery_verdict inconsistent
rationale delivered response does not conform to the advertised schema
conformance valid false · "missing advertised required property 'data'"
payment bound true · payer 0xC533Bf… · success true · problems []
response_sha256 9a8c0d27…
attestation ed25519, manifest hash d2ba8b95…, key published
charged nothing (free tier, 2 calls remaining)- Paid
- $0.00
- Quoted
- $0.05
- Verdict
- inconsistent, correct
- Payment bound to chain
- yes
- Signed
- Ed25519, verifiable offline
- Free calls left
- 2, shown in headers
- Others that caught it
- 0 of 5
- Wrong method
- 402, uncharged
Run this payment yourself
Free while the trial lasts. Works on any purchase you think went wrong.
curl -s -X POST https://groundcheck.seiche.info/attest-delivery \
-H 'content-type: application/json' \
-d '{"service":"<endpoint>","response_text":"<verbatim>","payment_receipt":"<tx>",
"advertised_schema":{"type":"object","required":["<promised field>"]}}' \
| jq '{delivery_verdict, rationale, conformance, payment}'
# then check the signature yourself: GET /attest/pubkeyReceipts: Called 2026-08-11 18:21 UTC from wallet 0xC533Bf5268A2F64aDDe58dcE380651f70Aa92D7A. No payment settled; the response carried x-groundcheck-free-remaining: 2. The subject's two charges were read from USDC Transfer logs on Base and are documented separately here. An earlier GET to the same path returned an uncharged 402 stating the route requires POST.