Verify a receipt
Drop a Veritar-issued receipt below. Your browser re-checks the cryptographic signature and event proofs using the same code that issued it. The file never leaves your device.
Drop a receipt PDF here
or
Accepts the .pdf receipt or the machine-readable .json.
Don't have one?
Look up a fingerprint code
The short code printed on a receipt (e.g. 6C2D-A832-10CF) is an
index into the public transparency log. Enter it to confirm a receipt with
that fingerprint is anchored in the public record. Your browser downloads the
log and re-verifies the entire chain itself — it doesn't take our word for it.
To see a receipt's full contents, drop the receipt above.
What this check proves
✓ Established here
- The receipt is signed by the embedded public key.
- Every listed event is committed under the signed Merkle root — nothing was added, removed, or altered after signing.
- The root is anchored in the public, append-only log — your browser downloads the log and re-verifies the whole hash chain and every signature itself, rather than trusting our server.
- When an identity certificate is attached, the signing key is bound to a named, regulated person by a trusted issuer — and the certificate is checked against the exact key that signed this receipt, so it can't be lifted onto someone else's work.
- The agent observes content copied from AI tools (claude.ai, ChatGPT, etc.) to the pasteboard, recording the length only — never the content. This is the headline signal for how much AI-originating text entered the work session.
Judge for yourself
- How rigorously the person's identity was checked at enrollment — self-asserted vs firm SSO + SRA register. The receipt states the enrollment method; weigh it accordingly.
- That everyone is shown the same log: ruling out a server presenting different logs to different people needs signed tree heads + gossip (the production transparency layer).
We never assert these silently — the verdict above shows exactly what was and wasn't checked.