Prove what your agent did.
Your own logs prove nothing — you wrote them. Tallwright witnesses every action your AI agents take and seals it into a record you cannot quietly change and an auditor can verify without trusting you.
payments-agent/eu-desk-04·sealing record 4,419·…
SHA-256 chained · co-signed out of your reach · verifiable offline
A log you control is not evidence.
An agent moves a payment, settles a claim, tells a customer something binding. The only account of what happened sits in a database your own engineers can write to. That is fine until someone asks you to prove it.
Then the question is not what your logs say. It is why anyone should believe them. Eleven months on, with a regulator or a customer’s lawyer across the table, an internal record is a statement, not evidence.
Tallwright
The witness layer for agentic software. One line of middleware in; evidence out.
- Promptcustomer asked to move 12,400 to a saved payeeverbatim, redacted per your policy
- Retrievedaccount balance · payee history · fraud scoreevery lookup the agent made
- Modelgpt-5.2-financial · temperature 0.1exact model and version that decided
- Decisiontransfer approved, under daily limitwith the rule that allowed it
- Actiontransfer.execute → core banking APIthe call, its parameters, the response
Written as it happens. All of it.
Not a transcript stitched together after the fact. The prompt, the retrievals, the model and version that decided, the rule that allowed it, and the exact call that went out — captured in the moment the agent acted, sealed before anyone had a reason to want it different.
When a dispute arrives, this is the difference between reconstructing a story from six systems and handing over the page.
Change one character.
Two consecutive records. The second one carries the first one’s digest — that is what binds them. Edit the amount below and watch a real SHA-256, computed in your browser, refuse to line up.
12,400.00 → 12,490.00·digest recomputed·link cut
- Record 4,417
- Agentpayments-agent/eu-desk-04
- PayeeDE89 3704 0044 0532 0130 00
- AmountEUR 12,400.00
- Digest…
- Record 4,418
- Expects…
- Found…
The record still reads plausibly. The next record no longer accepts it — and the break is visible to anyone who checks.
Three steps, in this order.
A record is struck, a witness countersigns it, and anyone can check the arithmetic. Watch it happen on the right — it never stops.
Record
Your agent calls Tallwright as it acts. What it was asked, what it retrieved, which model decided, what it did. Written at the moment of the action, not reconstructed from logs afterwards.
Witness
The record is co-signed by an independent witness outside your infrastructure and bound to the record before it. From that point neither your team nor ours can change it without the break becoming visible.
Verify
Hand any record to an auditor, a regulator or a customer’s lawyer. They check it against the chain themselves. Verification is arithmetic they can run, not a claim they have to take from you.
Teams whose agents do things that get disputed.
Banks and insurers
Agents that move money, settle claims or speak to customers. When one is disputed eleven months later, you produce the record instead of an argument.
Neobrokers and fintechs
You shipped agents faster than you built an operations team. This is the evidence layer you would otherwise write yourself, badly, under audit pressure.
Voice-agent platforms
Your buyers are regulated; their compliance review is your longest sales cycle. Ship them a verifiable trail and the review stops being your problem.
Firms with AI assistants
Legal and professional work where the file has to show who decided what, and when — including the parts a machine drafted.
Same record, different desk.
- Agentpayments-agent/eu-desk-04
- Actiontransfer.execute
- PayeeDE89 3704 0044 0532 0130 00
- AmountEUR 12,400.00
- At2026-08-20T09:41:07.284Z
The transfer your customer disputes eleven months later.
One plate is one record: struck as the agent acted, sealed before anyone wanted it different.
It meets your stack where it runs.
Sealing happens at whichever layer you trust least — framework, transport, or tool protocol — and lands in storage nobody can rewrite.
Core SDK
Framework-agnostic core. One conformance contract that every adapter has to satisfy.
Planned adapters · OpenAI Agents SDK · Claude Agent SDK · OpenTelemetry GenAI export
