Accept Orphograph receipts

Sooner or later, someone on your platform will answer a dispute with an Orphograph link: a claim that a file existed, unchanged, by a certain date. This page is for the engineer asked to decide whether that link means anything. Short answer: you can check it yourself, for free, without an account — and without trusting us.

Verify in ten lines

Every receipt id resolves at a CORS-open, unauthenticated endpoint. Fetch it, confirm the record exists, confirm the fingerprint matches the file you were given, and check whether the proof is pinned to Bitcoin:

const r = await fetch("https://orphograph.com/api/verify/" + id);
const rec = await r.json();
const fileHash = await sha256HexOf(file);      // hash the file YOU hold
const genuine =
  rec.found === true &&
  rec.hash_hex === fileHash &&               // exact file, byte for byte
  Boolean(rec.btc_pinned_at);                  // anchored in Bitcoin
// rec.created_at = the sealed time; treat !btc_pinned_at as "pending"

Or from a shell: curl https://orphograph.com/api/verify/<id>. The fields that matter: found, hash_hex, created_at, btc_pinned_at, calendars_ok. Folder receipts additionally expose per-file Merkle inclusion proofs at /api/inclusion_proof.

Show status, not screenshots

A live status pill for any receipt can be embedded on your pages — <img src="https://orphograph.com/api/badge/<id>.svg"> — it reflects the receipt's current verification state, not a claim frozen in a screenshot.

What accepting a receipt means

A verified receipt establishes exactly two things: this exact file existed in this exact form on or before the sealed date, and it has not been altered since. It does not establish who created the file, who owns it, or that its contents are true. Platforms that accept receipts well treat them as a timestamp of record — a fact that narrows disputes — not as a judgment.