Audrie in one page
What Audrie proves about a document, what it never sees, and where to start.
Audrie answers one question: was this exact document authenticated, by whom, and is that still true today?
It answers it without ever receiving the document.
The three claims
Your document never leaves your device
Audrie stores a fingerprint of your document, never the document. There is nothing in our systems that could reveal what any document said.
Signed to last decades
Records are signed with ML-DSA-65 (FIPS 204), a standard built to survive quantum computing. A signature made today still means something in thirty years.
Provable without us
Every record is committed to a public ledger Audrie does not operate. You can confirm a document is genuine even if Audrie is unreachable, out of business, or lying.
What a check tells you
Whether this exact file matches a record, who authenticated it, when, and whether that is still valid today. If any part of that cannot be fully substantiated, Audrie does not report the document as verified. There is no middle setting.
Checking a document is free and needs no account.
Start here
If you want to understand what Audrie does
- Why Audrie exists covers what stopped working, and what fixing it takes.
- How authentication works walks through authenticating a document, in plain terms.
- What you receive covers the two kinds of proof and what each is for.
- What Audrie never sees covers what is stored and what is not.
- Verifying a document covers checking something you were sent.
- What we do and don't claim sets out the boundary of Audrie's answer.
If you are building an integration
- Quickstart gets you a result from a cold start in under two minutes.
- Introduction covers the base URL, the one call that needs no account, and what a credential adds.
- How it works is the developer-facing version of authentication and anchoring.
- API keys covers issuing, scopes, rotation, revocation, and leaks.
- Verifying without Audrie confirms a record on Hedera yourself.
Reference
- Disclosure tiers covers which fields a response carries.
- Errors lists every status and error code, the envelope, and the rate limits.
- Pagination covers cursor paging on the verification log.
- API reference documents every endpoint, field and response, rendered from the published
contract. The raw contract is at
/docs/openapi.yaml.