The counterparty
“Why did you reject our standard escalator?”
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.
Northwind Legal · scenario №06
Contract — verified live
Anchored on Base Sepolia · Apr 26, 2026, 6:37 AM · tx 0x45dd5658…
✓ all 6 checks passOpen on easscan ↗
What Northwind Legal actually got
Scenario No.06
Northwind Legal · contract review agent · vendor MSA
Legal AI redlined a 36-month MSA against the playbook.
Argonaut Cloud proposed: 5% annual price escalator, mutual indemnification capped at fees paid. AI compared each clause to playbook v2.
What the AI considered
- Accept as-is (rejected: three out-of-policy clauses found).
- Counter with 12-month term (within negotiation latitude).
- Redline the 5% escalator → CPI cap.
What it chose
Redline set issued. General Counsel signed the change list before sending to vendor.
Why this matters
When an audit asks why this contract was structured the way it was, the receipt shows every clause flag, the alternative the AI scored lower, and the GC who approved the redline.
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.
External auditor
“Were contracts reviewed against a consistent rubric?”
Audit committee
“How are AI-assisted reviews different from a partner's?”
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 · 0x45dd5658111620…d7c73f13
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.