Public verification · no account needed
Verify a compliance receipt
A compliance receipt is a small file that proves a particular AI use of someone’s characters or brand was checked and cleared by LicenseOS. Think of it like a paid receipt or a building permit — it shows you had permission, and it’s digitally stamped so it can’t be faked.
It’s a tiny piece of text you can save, attach to your work, or email.
Anyone — a client, a store, a lawyer — can check it on this page in one click.
Change a single character and it stops verifying. You can’t fake or edit it.
Check a receipt now
Paste a receipt’s text below, or load a working sample to see exactly how it works — no signup, nothing to install.
How do I get a receipt?
You get one automatically every time you run a compliance check. New to this? Start with the no-code path.
- 1Get a license
Pick some IP and get a license (or use the built-in demo sandbox). You’ll receive an API key.
Browse IP - 2Run a check
Describe the use and run it — no code needed in the in-app Playground, or one API call from your app.
Open the Playground - 3Keep the receipt
The result includes a
receipt+signature. Download it, attach it to your output, or share this verify link.
Developers: get & verify a receipt in code
// Your check / generate API response includes a receipt:
{
"decision": "allow",
"approved": true,
"riskScore": 12,
"receipt": { "v": "1", "ipProperty": "moonberry-grove", "decision": "allow", ... },
"receiptSignature": "losr1:9b4e…" // ← the signature that makes it tamper-proof
}
// Anyone can verify it later — no API key needed:
curl https://licenseos.vercel.app/api/v1/decisions/verify \
-H "content-type: application/json" \
-d '{ "receipt": { ...the receipt... }, "signature": "losr1:9b4e…" }'
// → { "ok": true, "valid": true }What makes a receipt court-credible
A receipt isn’t just a stamp — it’s the end of a chain (sign → timestamp → tamper-evident log → public verify → evidence bundle), each layer honest about what it proves.
Proves LicenseOS issued this exact record and it hasn’t been altered. Does not prove the use is lawful.
ES256 today (verifiable against the public key). KMS/HSM sole-control is the next upgrade.
Records when the decision was made. Strongest when a third party attests the time, not us.
Self-attested server clock today, honestly labeled. An RFC-3161 qualified timestamp authority drops in next.
Any edit or reorder of a past entry breaks every later hash, so tampering is detectable. Does not prove a use was permitted.
Live: each entry hash-links to the previous one, with an independent head witness against truncation.
Anyone can re-check the signature against the published public key — no LicenseOS access. We can’t forge our own evidence.
Live: a public verify endpoint + a published JWKS public key set.
One self-contained file an insurer, regulator, or court can re-verify independently — receipt, key, timestamp, hashes, and an explicit “proves / does not prove.”
Live: downloadable signed bundle + human-readable summary + an FRE 902(13) certificate template.
What a receipt is — and isn’t.
this receipt is evidence of a documented generation-time process — not proof of compliance, admissibility, or non-infringement.
Common questions
Do I need an account to verify?
No. This page is public. Anyone you share a receipt with can check it here.
Is my receipt stored or sent anywhere?
No. We only re-check the signature math and tell you pass/fail. The receipt isn’t saved.
What does “invalid” mean?
Either the receipt was edited (even one character), or it wasn’t issued by LicenseOS. A genuine, unaltered receipt always passes.
How is this different from a Content Credential?
A receipt proves a decision was cleared. A Content Credential is provenance stamped on a generated asset — verify those by ID at /verify/<credential-id>.