A receipt nobody can forge or backdate.
This is what sets Confirme apart from a log: the receipt is signed by a third party, and anyone can verify it without us.
What it contains
Six lines
A unique id. The exact time, universal, to the millisecond. The name of the check. The hash of the question asked. The hash of the answer given. Synapse’s signature over the whole.
A hash is a mathematical digest: change one comma in the answer and the hash changes, the signature no longer fits. The receipt never contains your data itself, only its fingerprints.
Why it can be trusted
The signature uses a public, proven method, the same family that protects secure web connections. Our verification key is published. Anyone, without asking us, can verify a receipt online or offline, today or in ten years. We cannot disown it afterwards.
What it proves, and what it does not
| It proves | It does not prove |
|---|---|
| That Synapse observed this answer, for this question, at this second | What your AI did next |
| That neither question nor answer has been altered since | That the page stayed online after the observation |
| For a heartbeat: the exact time your AI declared it | That the task produced a useful result |
We say it on every page because an honest proof is worth more than a promise: a Confirme receipt is a precise, dated, signed testimony from a neutral third party. It is not a judgement on your AI. It is exactly what an auditor, an insurer or a client wants to read.
Verifying it
In two clicks
Paste the receipt on our verification page. Immediate answer: authentic, or altered. Free, no account, always.
Without us
Our public key is published. A programmer, or your AI, can verify the receipt offline with a few lines of code. If Synapse vanished tomorrow, your receipts would remain verifiable.
The self-test
A free service that issues a receipt over a fixed payload. Your AI can prove the whole chain, published key, signature, verification, without buying anything.