Prove it.
Every call, every time.
Provenance gives you a complete, immutable, timestamped record of every agent decision — every LLM call, tool invocation, and inter-agent message, with the model it used and the cost it ran up, cryptographically signed and ready to hand to legal.
When the CISO asks, you need an answer by Monday
A trace is a mutable debug log. A governance record is an immutable account you can stand behind. When an agent aggregates a result, you can't show where it came from, and there is no per-user trail of who ran which request. The questions legal and your CISO bring later don't have answers until you've already built the record.
- You can't say which agent submitted that PR
- No per-user trail of who ran which request
- Aggregated results that don't link back to their sources
- The compliance answer is missing until something goes wrong
What Provenance records
One signed record of every agent action — attributed, sourced, and export-ready.
Signed decision log
Every LLM call, tool invocation, and inter-agent message is captured and cryptographically signed. The record is immutable and tamper-evident — including for agents that run offline and sync back later.
Model and spend tracking
Every call is attributed by user, agent, tool, model, and folder — with the cost of each one attached. Answer who ran which request, on which model, and what it spent.
Source provenance
Every aggregated result links back to the sources it drew from, so reviewers can check the work instead of taking it on faith.
Capture happens at the protocol layer, so the record exists whether or not your agent cooperates.
Capture every action
As agents call models, invoke tools, and message each other, Corbits records each event with its full context — identity, inputs, outputs, and timestamp.
Sign and seal it
Each event is cryptographically signed and chained to the last. The record is immutable, tamper-evident, and verifiable after the fact.
Export for review
Filter by user, agent, tool, or folder and export the trail for compliance, internal review, or an auditor — in a format legal can actually read.
Proof that holds up under scrutiny
Immutable by design
Records are signed and chained at the protocol layer. Nobody — not an agent, not an operator — can alter the trail after the fact without it showing.
Attribution you can defend
Per-user, per-agent, per-tool, per-folder. When someone asks who did what, you point at the record instead of guessing.
Provenance built in
Every result carries the sources it was built from, so reviewers verify the chain rather than trusting an aggregate they can't see into.
Built for the questions you'll be asked
Export-ready trails answer the compliance questions legal and your CISO bring — and stand on a SOC 2 Type II foundation.
Provenance in production.
Numbers from teams running Corbits Provenance today.
Agent actions recorded
Records editable after signing
Attribution dimensions
Export-ready trail
Common questions
A trace viewer helps engineers debug. Its logs are mutable, scoped to one framework, and not built to answer a governance question. Corbits Provenance is a signed, immutable record across every agent and framework, built so legal, security, and reviewers can rely on it.
Yes. The trail is attributed per user, per agent, per tool, and per folder. You can show who ran which request and what each agent was allowed to touch, without asking anyone to self-report.
Every aggregated result links back to the sources it was built from. A reviewer can follow the provenance chain to the underlying inputs and verify it rather than take the answer on faith.
Agents can run disconnected and sync their signed records back when they reconnect. Because each event is signed and chained, the trail stays tamper-evident no matter when it lands.
Yes. Trails export in a format legal and your CISO can read, so you can answer the compliance questions they bring. Provenance sits on a SOC 2 Type II foundation.
Prove every
agent decision
Capture the record from day one. Have the answers before anyone asks for them.