Financial regulator
“How does the AI handle false positives?”
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.
Shinhan · scenario №07
Fraud hold — verified live
Anchored on Base Sepolia · Apr 26, 2026, 6:37 AM · tx 0x87094173…
✓ all 6 checks passOpen on easscan ↗
What Shinhan actually got
Scenario No.07
Shinhan · fraud-detection AI · real-time card flow
A fraud AI held a charge instead of denying it outright.
₩820K · Macau merchant · cardholder usually shops in Korea. Anomaly score 0.74. SMS step-up triggered.
What the AI considered
- Allow — appears benign (rejected: too lenient).
- Hold + SMS step-up.
- Outright deny — too aggressive (rejected).
What it chose
Hold + step-up. Released after customer authenticates.
Why this matters
When the customer disputes the friction, Shinhan can show exactly which signals fired and which alternatives were rejected — none of it editable after the fact.
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.
The cardholder
“Why was my purchase blocked?”
A regulator drafting new rules
“What does a defensible audit trail look like?”
What this proves — in plain English
This decision happened.
Recorded on Base Sepolia at April 26, 2026 at 3:37 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 · 0x87094173a6f670…20b0f828
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.