For leaders at regulated enterprises running AI agents
When someone asks what your AI did, the answer already exists.
A regulator, an auditor or a court will ask what your AI agents did. Answering by hand takes your most senior engineers off their work. With BitExact, every run from the day it starts recording is already recorded and sealed: you hand over exactly what was asked, nothing more, and they check it themselves.
The request arrives
“Every decision your credit agent made in March.”
It comes from a supervisor, your internal audit, or the other side in a dispute. It has a deadline. And it lands on somebody’s desk.
- A supervisory authority
- Internal audit and model risk
- A court, in discovery
- A customer’s complaint
Your best engineers answer it. Instead of their real work.
No one owns “the logs”. The trail of one decision is spread across systems that were never built to answer a regulator:
- The model providerprompts and answers, in their console
- Your applicationits own logs, in its own format
- The tool serverseach with its own retention, if any
- The data storeswhat the agent read, as it is now
- What rotated awaypast retention, already gone
- Tools that never loggedno record exists to collect
So the request goes to the people who know where everything lives: your most senior engineers. They come off the roadmap and off critical projects to do it. That is not a risk to plan for. It is how a manual answer gets made, every time.
- FindWork out which systems the agent touched in March, and who has access.
- ExtractPull exports from each, in whatever form each one gives.
- ReconcileLine up clocks, ids and formats until one decision reads as one story.
- CheckConvince yourselves nothing is missing or was changed.
- TrimCut it to what was asked, and strip what must not go out.
- ExplainWalk legal, and then the regulator, through how it was assembled.
Your arithmetic
Count what they didn’t ship while they did it. Put in your own numbers; only you know them.
And the next request starts from the beginning again.
03 · Two risks in a manual answer
A hand-built answer can be wrong in two directions.
-
Inaccurate
Stitched together, and open to doubt.
Logs copied out of five systems are only as good as the weakest copy. Anyone with access could have edited a line, and nothing would show it. The first question back is how you know.
-
Too much
The kitchen sink, and new exposure.
Under a deadline, sending everything feels safe. It hands over data nobody asked for: other customers, other decisions, personal data. Each one is a new question you then have to answer.
Accurate and minimal, both at once, is the hard part.
The answer already exists before anyone asks.
-
One sealed record per run
Each model and tool call your agents make through BitExact is recorded where the agent makes it, in order, each step linked to the one before, and the run is sealed when it ends. Not fragments in five systems: one record, and any later change shows.
-
Including tools that log nothing
A tool that keeps no log of its own is still on the record, because its call and its result are captured where your agent makes the call.
The condition, plainly: the call has to go through BitExact. A call made around it is not in the record, and BitExact never claims it is. Where it could not record, the record says so, with the reason.
-
One pack, scoped to the request
Answering is one evidence pack, cut to what was asked: a workflow, a period, an agent, a case, or the person a decision was about. Nothing outside the scope travels with it.
-
Sensitive fields never stored
Card numbers, IBANs (international bank account numbers) and credentials are scrubbed before anything is written, by default, and your own rules can add more. Removing a value later can be made to take two people: one asks, a different one approves, and the record still verifies.
-
They check it without you
The regulator runs the free, open-source verifier on the pack on their own machine, offline. No BitExact license, no account, and no call to you or to us.
-
It stays in your network
BitExact runs entirely inside your infrastructure. There is no BitExact service and no telemetry, and the license is checked offline.
Start recording before anyone asks.The answer exists from the day BitExact starts recording. It can answer only for what it has recorded, never for the months before.
The same request, answered from the record.
Four steps, a couple of seconds each. Set them against your own count above.
The request arrives: every decision your credit agent made in March. Your team picks the scope: the credit-decision workflow, 1 to 31 March. One evidence pack goes out, holding only the runs in that scope, with sensitive fields scrubbed before they were ever stored, signed by your deployment’s key. The auditor runs the open verifier on it offline. It prints: OK, evidence pack, 43 runs verified, signed, recorder-attested. In plain words: nothing in these runs was changed or removed, every run is sealed, and the pack is signed with the key the auditor pinned. Pass. No call to you, and no call to us.
No call to you. No call to us.
Illustration: the workflow, month, run count and file name are examples. The first line of step 4 is the open verifier’s own verdict, shortened; the words under it say what it proved. Where the record has a capture gap, that line counts it.
The questions you will ask.
What does it take from our team?
A few lines per agent, not a rewrite. Your engineers wrap the model client and mark each tool, or point the agent’s model client at the BitExact recorder. Python, TypeScript, Go and Java are supported directly. With your license issued, the first sealed run takes under 30 minutes. One prerequisite: the server that runs the recorder needs a TPM 2.0, the standard security chip in most modern servers.
Where does our data live?
Inside your network, and only there. There is no BitExact-hosted service and no telemetry, and nothing phones home. The only things that can leave, and only if you turn them on, are a hash sent to a timestamp authority, signed log checkpoints sent to the outside witnesses you choose, notifications to your own systems, and calls to your own AWS KMS when you keep keys there; none of them carries recorded content.
What happens if BitExact fails?
Your agents keep running. If BitExact cannot record a call, the call goes through as it would without BitExact. The gap is written into the record with its cause, and every check of that record shows it. How each way of deploying it behaves, for your engineers.
Does it capture everything?
It captures what passes through it, and says where it stops. Every model and tool call made through BitExact is recorded. A call your agent makes around it is not, and no verdict ever claims the record is complete. Where it could not record, the gap is declared, counted and reported.
Does it make us compliant?
No. It supports your record-keeping. It gives you evidence and states where that evidence stops; whether you meet an obligation is your determination. The EU AI Act’s record-keeping duty for stand-alone high-risk systems, creditworthiness assessment among them, is scheduled to apply from 2 December 2027, and that date may move again. The compliance mapping.
How is it licensed?
A fixed-term pilot, then an annual license in one of two editions: Department, for a band of production agents, or Enterprise, for unlimited production agents. Never per seat, per run or per event: recording more never costs more, staging and test agents are free, and the verifier is free for everyone. How it is licensed.
Measure the saving in your own company.
A pilot runs 60 to 90 days on one deployment, recording one of your real agents in production. Near its end, we take one request about the period it recorded and answer it with an evidence pack, timed. You set that time against how long your last request like it took by hand, from your own records. The saving is measured in your company, not claimed by us.
- 1 · Scope
One conversation
The agent to record, the kind of request to answer, and who will check the evidence.
- 2 · Record
On your infrastructure
The recorder, the store and the keys run inside your network, recording real traffic.
- 3 · Compare
One request, answered from the record
An evidence pack your auditor verifies offline, timed, beside what your last manual answer cost. You keep both numbers.
Continue and the pilot fee is credited in full against your first annual license. One prerequisite to know now: the server that runs the recorder needs a TPM 2.0, the standard security chip, that it can reach.
or write to sales@bitexact.ai