AOTrust

Cryptographic proof that a document, code file, AI output or any artifact existed at a specific time. A 239-byte Ed25519-signed receipt (PDR), a leaf in an append-only Merkle log, and a root committed to the NEAR blockchain - verifiable by anyone, without trusting us.

PDR $0.01 · x402 USDC (Base) FreelanceShield $0.10 · USDC (Base) Evidence bundle $0.02 free tier 5 / 24 h hourly cumulative anchor RFC 9162 proofs

Try it

Protect a file in 30 seconds

No wallet, no signup. Free tier: 5 proofs per 24 hours, shared with FreelanceShield. Within the hour the proof is written to the NEAR blockchain - after that it can be checked even if AOTrust disappears.

Drop a file here or click to choose

○ SHA-256 computed locally - the file never leaves your browser
○ Receipt signed by the notary - 239 bytes, Ed25519
● Queued for the hourly NEAR anchor (≤1h) - the root is committed on-chain every hour

What you getA receipt ID and a link like verify.aotrust.link/s/2ac35c78 - exactly what you send to a client. Choose a file above to create yours.

Example already anchored: verify.aotrust.link/s/44ef8cb3

Three ways in

Notarize an artifact

$0.01 · x402

POST /notarize with your SHA-256 hash. HTTP 402 quotes the price; pay with an EIP-3009 signature (x402, no account) and get pdr_b64.

Quickstart →

Evidence bundle

$0.02 · proof pack

For any recorded hash: the PDR plus its place in the anchored log - cumulative root, inclusion path (RFC 9162), NEAR transaction and an offline verification recipe.

API reference →

FreelanceShield

$0.10 · per file

For freelancers: prove you created the work before sending it to a client. A PDF certificate you can attach to the message, verifiable by anyone.

shield.aotrust.link →

$0 Free tier: 5 proofs per 24 hours, no wallet, no signup

Why people use it

Prove you patched it

Verifiable receipts for security hygiene - patch, rotation and scan evidence that an auditor or insurer can check without trusting your logs.

Security receipts →

Verify us, don't trust us

Public append-only Merkle log: latest anchor, in-browser RFC 9162 inclusion and consistency checks, keys via JWKS and did:web.

Transparency log →

Bilateral receipts (v0x04)

Two-party attestation: the agent signs, the notary binds both signatures with a public binding hash. Specification and live test vector.

Specification →

FreelanceShield

For freelancers: prove you created the work before sending it to a client. PDF certificate, $0.10 per file.

shield.aotrust.link →

Notarize your releases

We eat our own food: every release we publish is notarized on the way out. PyPI aotrust-protocol 2.5.1 and aot-ev1 0.1.2 carry their own Shield ID in the job summary.

Versions and receipts →

Proofs for AI agents

Machine-readable evidence: an AOT-EV1 bundle an agent can attach to its output, and an MCP server so the call is one tool invocation, not a custom integration.

AOT-EV1 bundles →

How it works

01Hash the artifact locally (sha256sum file). The file never leaves your machine.

02Send the hash to the API. The notary signs a receipt and returns it; the hash becomes a leaf in the append-only log.

03Hourly (when something new exists) the cumulative Merkle root is committed to NEAR. Later anyone can prove inclusion and that the log was never rewritten.

Append-only means we cannot silently rewrite the past - consistency proofs would expose it. It does not mean we publish everything: we can choose not to add new entries.

Machine entry points

API openapi.json · llms.txt api / docs
MCP POST https://api.aotrust.link/mcp (streamable-http) · keys JWKS · did:web
anchors /v1/anchor/status · x402 /.well-known/x402