Check a receipt

Paste a receipt, or the whole JSON response a call returned. Your browser recomputes the claim id, recovers the signer and compares it to the key you pin, recomputes the charge, checks the delivered text, and looks up the settlement on chain. Nothing you paste is sent to us.

Receipt or response JSON Pinned broker key (filled from /v1/receipt-key; replace it with a key you pinned earlier to check against that)

Optional: prove it is yours, and check the delivered bytes

The settlement txid you paid (from readSettlement(res).transaction, never from the receipt) The completion text you received (filled in automatically when you paste a full response) What you sent (the messages array as JSON, or the plain prompt text)

What each check proves

Signature. The claim id is sha256 of the receipt's signed fields, and the signature must recover to the key you pinned. Change any signed field and both break.

Charge (usage receipts). The sats must equal the published formula over the receipt's own token counts and rates. More than the formula is an overcharge.

Delivered bytes. outputDigest must equal sha256 of the text you received, so the receipt covers this exact answer.

Settlement (x402 receipts). The transaction must exist on chain and pay the receipt's address at least the amount. A receipt alone is a bearer object; it is yours only when its txid matches the payment you made.

Scripted checks: verifyX402ReceiptFull and verifyReceiptChain in @bsvkey/x402-bsv-client. Spec: usage-receipts.md.

Check a receipt

What the receipt says

What each check proves