attest — documentation

A receipt is one signed record of what an agent was recorded as doing at the boundary that governed it. This page says what that proves, what it does not, and how to check one yourself.

What a receipt proves

ProvedHow
The record was issued by that keyEd25519 signature over a domain-separated digest
It has not changed sincechain.hash recomputed from the bytes; a mismatch is a rejection
It was not re-encoded in transitcanonical form checked against the bytes received
It sits where it claims in its chainsix chain conditions, all reported separately
A third party saw it exist at a momentinclusion proof in a transparency log, verifiable offline

What it does not prove

These are non-claims, not disclaimers. A record that promises more than it holds is worse than no record, because the reader cannot tell where the support ends.

Endpoints

PathWhat it does
POST /verifyverify an artifact: schema, emptiness, provenance, mandate
POST /log/registerregister a statement in the log, get an inclusion proof
GET /log/headsigned tree head: size, root, signature, public key
GET /log/proof/<i>inclusion proof for leaf i
GET /log/consistency/<n>proof that the tree of size n is contained in the current one
POST /mcpMCP 2026-07-28, stateless; tools verify_artifact and verify_artifact_batch
GET /verify-offlinethe same verifier, inlined, no network calls

Check a receipt offline in three steps

1. open https://attest.rta.lat/verify-offline and save the page
2. paste the receipt text exactly as you received it, and the issuer public key
3. read the verdict — VALID means signature, canonical form and hash agree

The same corpus is published: conformance/receipt-vectors.json, CC0. If your implementation disagrees with ours on those bytes, that disagreement is the useful result.

हिन्दी — सारांश

रसीद एक हस्ताक्षरित रिकॉर्ड है: एजेंट ने नियंत्रण-सीमा पर क्या किया, यही दर्ज है।

Русский — коротко

Квитанция — одна подписанная запись о том, что агент сделал на границе, которая им управляла.