The customer
“Was the refund really approved? When?”
Public verifier
See an AI decision prove itself.
Pick a real scenario below. Watch what the agent considered, what it chose, and what we'd show a regulator or a judge if anyone challenged it. Every example is anchored on Base Sepolia right now — clickable, checkable, can't be edited.
Bloom Co. · scenario №01
Cs refund — verified live
Anchored on Base Sepolia · Apr 26, 2026, 6:36 AM · tx 0x2235d540…
✓ all 6 checks passOpen on easscan ↗
What Bloom Co. actually got
Scenario No.01
Bloom Co. · DTC supplement brand · 5 AI agents
A refund bot returned ₩42,000 to a sleepless customer.
Order placed 9 days ago. Customer asked for a refund. The CS bot evaluated against refund policy v2.1 and approved.
What the AI considered
- Deny — package opened (rejected: still inside the 14-day window).
- Approve — first-time refund, no abuse signals.
What it chose
Approved. Shopify refund issued; customer notified.
Why this matters
Three months later, the customer disputes the charge. Bloom must prove the refund followed a real policy — not a hallucination. trace.ai's record holds.
Who can ask, and what they ask
The same record satisfies very different questioners. Each gets the same answer — and none of them have to trust the other party's word for it.
Stripe / the bank
“Was it processed under the merchant policy?”
A future auditor
“Did the AI follow refund policy v2.1?”
What this proves — in plain English
This decision happened.
Recorded on Base Sepolia at April 26, 2026 at 3:36 PM KST. The transaction is permanent and publicly visible — try editing it.
These were the inputs.
Every prompt, every retrieved context, every alternative the AI considered — fingerprinted into the same Merkle tree. Change one byte and the entire root invalidates.
This was the chosen output.
Not just what shipped — what was rejected, scored, and overridden. A future investigator can see the full reasoning, not just the final answer.
A neutral third party witnessed it.
trace.ai anchored the root with 0x4eC5A687…; the operator signed the payload with 0x1e6d0f5e…. Neither party can produce this evidence alone.
tx · 0x2235d540633130…5e8ecd5a
Run a simulation
Watch a decision earn its receipt — across 7 industries.
Pick a scenario. Press play. Each step shows a different artifact — the ticket, the score bars, the signature, the Merkle tree, the block, the verifiers — so you see the proof being built. Same protocol works for e-commerce, finance, healthcare, HR, insurance, and legal.
Currently simulating
CS bot processes a refund
Next
Want to put your own AI agent on the record?
One npm install. One SDK call. Every decision gets a permanent, independently verifiable receipt.