Receipts for what your systems did.
Send one signed request for each event that matters. ATTESTRAS keeps an append-only record and gives you a receipt anyone can verify, without an account and without seeing your data.
100 receipts a month free. No card. Proof of a record, never of the truth.
Make a sample receipt
Type an event, create a receipt, then change one character and watch the check fail. It runs in your browser: nothing is sent or stored, so this is a sample, not a usable receipt.
- Proof ID
- Receipt hash
- Recomputed
The exact bytes hashed, and how to check them yourself
The receipt hash is the SHA-256 of these canonical JSON bytes. Paste the command in a terminal and you get the same hash without trusting this page.
Needs JavaScript. Without it, the quickstart below makes a real receipt.
From zero to a verified receipt in about two minutes.
Get a key
Enter an email, click the link we send, copy your key. No card, 100 receipts a month free.
Paste four lines
curl -fsSO https://attestras.vercel.app/sdk/attestras.py
export ATTESTRAS_URL=https://attestras.vercel.app ATTESTRAS_SOURCE=my-first-source
export ATTESTRAS_KEY_ID=ak_xxxxxxxxxxxx ATTESTRAS_SECRET=atsec_xxxxxxxx
python3 attestras.py demoPrefer Node? attestras.mjs takes the same variables.
Open the link it prints
The command creates one receipt and prints a verify link. Open it: the check needs no account.
{
"message": "Created",
"proof_id": "pg_0f3c9a7e51b24d08a6e1c3d7b92f4a10",
"proof_hash": "9b1d5e…64 hex characters…c07a",
"verify_path": "/verify"
}Four hops, one receipt.
- 1. Your system
Signs the exact bytes
HMAC-SHA256 over the body, timestamp, request ID, source and key. A 30-second window stops replay.
- 2. ATTESTRAS
Binds the tenant from the key
The key decides whose receipt it is. There is no tenant field in the request to get wrong.
- 3. Append-only store
Hashes once, stores once
Canonical JSON, SHA-256, INSERT only. Retrying the same request returns the same receipt.
- 4. Anyone
Checks the receipt
A proof ID and a hash. The public verifier shows seven fields, never your actor, assertion or file link.
What a receipt proves, and what it does not.
Most attestation pages blur this line. We put it first because your auditors will check it.
A receipt proves
- This exact record was accepted from one of your signing keys.
- It has not changed since it was stored (the hash is recomputed on every read).
- When our server recorded it.
- Your tenant, actor and assertion stay private to you.
A receipt does not prove
- That the statement in the receipt is true.
- That the artifact is lawful, safe or high quality.
- Independent time evidence: there is no external timestamp authority or public-ledger anchor yet.
- Certification, regulatory approval or legal admissibility.
Read the full trust boundary, including what is shipped and what is not.
Check a receipt in ten seconds.
No sign-up. The values travel in the request body, not the URL, and the page is never cached or indexed.
Boring in the places that matter.
Safe to retry
The request ID is an idempotency key. Same bytes return the original receipt. Changed bytes return 409 instead of silently overwriting.
Signed exact bytes
The signature covers the body, timestamp, request ID, source and key. A 30-second window stops replay of stale requests.
Tenant bound by key
Which tenant a receipt belongs to comes from the key, never from the request. There is no tenant field to get wrong.
Append-only by design
Database triggers reject UPDATE, DELETE and TRUNCATE on receipts, and our production runtime role is never granted those rights. Every read recomputes the hash.
Privacy backstop
Payloads containing email addresses, phone numbers, US Social Security numbers or UK National Insurance numbers are rejected. Actors are pseudonymised per tenant before storage. It is a backstop, not a licence to send personal data.
One-file clients
Python and Node, no dependencies, plus an OpenAPI document. Read the docs.
Pay for receipts, not seats.
Free
Try the whole flow. No card.
No card needed.
- 100 new receipts a month
- 2 active API keys
- Unlimited verification
- Python and Node clients
- Hard stop at the allowance, no surprise bill
Build
For one product shipping real receipts.
or £290 a year (two months free)
- 5,000 new receipts a month
- 10 active API keys
- Unlimited verification
- Python and Node clients
- Hard stop at the allowance; upgrade any time
Scale
For a platform team issuing at volume.
or £1,490 a year (two months free)
- 50,000 new receipts a month
- 50 active API keys
- Unlimited verification
- Python and Node clients
- Hard stop at the allowance; contact us for more
Prices include any VAT. Need more, a private region or a contract? Talk to us.
Plain answers.
Is this a blockchain or a timestamp authority?
No. A receipt is a record in our database with a SHA-256 hash. The time is our server clock. There is no RFC 3161 timestamp authority. Optional OpenTimestamps anchoring is built but off until we have run it against the live calendars, and the trust page shows its status.
Can I use a receipt as legal evidence?
We make no claim either way. Whether a receipt helps depends on your jurisdiction and facts. Take legal advice before you rely on it.
What does the public verifier reveal?
Verified or not, the proof ID, the receipt hash, your source name, the artifact SHA-256, the claim schema and the recorded time. Never the tenant, the actor, the assertion text or the artifact link.
What counts toward my allowance?
One new receipt is one unit. Safe retries of a request you already sent, and every verification, are free.
Can a receipt be deleted?
Not while your contract runs: immutability is the product. Your sign-up data, though, is yours: close the account any time and it is deleted straight away.
See your first receipt in about a minute.
Enter an email, confirm it, paste one command. Then open the verify link it prints.