Tutti i documenti legali sono disponibili solo in inglese e solo la versione inglese è giuridicamente vincolante.
Traduci con Google Traduttoresi apre in una nuova scheda; solo come riferimentoHow anyone can check an Agined receipt without us, offline if they want, with our libraries, the /verify page or a few lines of their own code, and what each result means.
Last updated October 29, 2026.
A receipt can be checked by anyone who has it and our public key: a counterparty, an auditor, a court. You do not need an Agined account, an API key or our agreement, and you do not have to tell us you are doing it. The Verifier Terms say what a valid receipt lets you rely on.
In plain language: take the receipt, take our public key, check the signature. If it matches, nobody has changed the receipt since we signed it.
Every verifier, ours or yours, does the same four things:
signature member.kid equals the receipt's signatureKeyId.| Result | Meaning |
|---|---|
| Valid | The receipt is exactly what Agined signed with the named key |
bad_signature | The signature does not match. The receipt was changed after signing, or was never signed by that key |
unknown_key | The key it names is not in the key set you checked against |
malformed_envelope | It is not a well-formed receipt, for example body.type differs from type |
redacted | Fields were removed after signing, so the signed bytes cannot be rebuilt. An unredacted copy still verifies |
A valid result says nothing about whether reported facts are true. Read the receipt's type and the Receipt Practice Statement to see what it attests.
| Way | Network needed | Status |
|---|---|---|
| The /verify page | Only to fetch the key set; the check runs in your browser | Available |
@agined/verify for JavaScript and TypeScript | Only to fetch the key set, unless you pass pinned keys | Published on npm |
| Your own code, in any language with Ed25519 and a JCS library | None, with pinned keys | Always possible; see Verify in your own code |
| The receipt export | None: each export contains the key set and a verify.mjs script | Available in the dashboard |
There is no command-line tool. The status of each library is kept current on SDKs, CLI and GitHub Action.
Verification needs the network only to fetch our key set. To verify with no network at all, or long after the event:
kid and x of the key you rely on, as Key management explains;kid, in a system you control.The receipt format is designed so that version "1" receipts stay verifiable for good; see Format versions and long-term verification.
Verifying receipts in the documentation publishes a known-answer receipt and its key. Your verifier should accept it, and should reject the same receipt with any single character changed.
If a receipt verifies but you believe we did not issue it, or a genuine receipt fails, write to security@agined.com with the receipt.