proof-session
$ agent-receipts init proof-demo
✓ workspace created and checked out in 4.2s
AgentReceipts SDK v0.1.0
0G Mainnet · receipt signer ready
~/agent-receipts/examples/demo-agent
? press esc to interrupt
Proof-first infrastructure

Prove what AI agents
actually saw, did,
and returned.

Every tool call an AI agent makes is signed, chained, stored on 0G Storage, and anchored to 0G Chain mainnet. No trust me logs. No unverifiable claims. Just cryptographic receipts.

Sign
ed25519 receipt chain
Store
0G Storage batch records
Anchor
Merkle roots on 0G Chain
Workflow

Verification that behaves like infrastructure, not logging.

01
Agent makes a tool call

The SDK wraps the request, captures the URL, method, and response body hash before an agent can rewrite the story.

02
Receipt signed and stored

Every receipt is ed25519 signed, linked to the previous receipt, and committed into a durable batch on 0G Storage.

03
Batch anchored on-chain

The anchor service builds a Merkle tree and publishes the root to the ReceiptAnchor contract for independent verification.

Live receipts

Inspect real receipts, verify their signatures, and confirm that the batch resolves to an on-chain anchor.

Loading receipts…

Tamper demo

Reject modified receipts the moment proof breaks.

Mutate a receipt hash and the verification chain fails immediately. This demonstrates the difference between logs an agent can narrate and receipts that third parties can prove.

Run the e2e flow first to load at least one receipt for tamper testing.