OREOASIS← Home
Why receipts

Your agent acted. Now prove it — to someone who wasn't there.

AI agents are doing real things now: refunding a customer, moving money, closing a ticket, sending a message on your behalf. When someone later asks “did that actually happen, and exactly what did it do?” — what do you show them?

Logs aren't proof

A log or a screenshot is something you wrote about yourself. You could change it. So could anyone with access. That's fine for debugging — it's useless the moment a customer, an auditor, a partner, or a regulator has to believe it. “Trust me, here's my log” is not an answer to a dispute.

A receipt is

A receipt is a record of one action that's signed the instant it happens, linked into a tamper-evident chain, and anchored to a public log so it can't be quietly backdated or rewritten. Every receipt gets a public link. Whoever opens it re-checks the signature in their own browser — they don't have to trust your backend, and they don't have to trust ours. That's the difference between a claim and a proof.

Whose proof it is

Receipts point one direction on purpose: Oreoasis proves your work for you, to someone who doubts you — never about you, to someone who commands you. The party doing the work holds the key. It's the opposite of surveillance: it's the evidence that lets you act with confidence and settle a dispute in your favor.

Free to verify, forever

Anyone can verify any receipt at no cost, forever — including receipts from cancelled accounts. We never gate verification and we never take a verify link offline. The paid tiers buy features (longer history — how far back you can pull your own receipts through the API and exports — per-receipt anchoring, exports, removing our footer); the public verify link never expires on any plan, and the proof itself is always free.

Ready? The quickstart gets you a verifiable receipt in under five minutes.