Proof engine for AI agents

A proof engine for the decisions your AI agents make.

DarkMatter is a proof engine for AI agents, not just another audit log.

Commit a record at the moment of decision. It is sealed, stored outside your system, and verifiable by anyone, even if DarkMatter were to go away.

Independent
outside your system
Sealed
at the moment it happens
Verifiable
by anyone, anywhere
DarkMatter · example
illustration
✓Payment approved, $84,000 to Acme Corp
example record · ctx_7f3a9b
✓Customer data shared with billing provider
example record · ctx_7f3a8c
✓Model selected: claude-sonnet-4-6
example record · ctx_7f3a7a
no DarkMatter account needed to verify
Python SDK TypeScript SDK LangGraph · soon Anthropic SDK OpenAI SDK CrewAI · soon AWS Bedrock · soon Local models REST API Self-host · soon
Python SDK TypeScript SDK LangGraph · soon Anthropic SDK OpenAI SDK CrewAI · soon AWS Bedrock · soon Local models REST API Self-host · soon
The problem
01

Your logs live inside your system

Logs, databases, and audit trails all live in systems you control. When something goes wrong, you are asking people to trust you. Some situations do not allow that.

02

By the time you need proof, it is too late

You cannot retroactively create an independent record. Evidence that appears after an incident is not evidence. The record has to exist before anyone knew it would matter.

03

AI decisions are too consequential to leave unverified

Automated decisions about money, safety, and compliance need a record that works without your involvement. Not logs you wrote. Not a dashboard you built.

How it works

One line of code. A record that stands on its own.

01

Add one line at decision time

Call dm.commit() when your agent makes a decision. It takes under a second and does not change how your agent works.

dm.commit(payload={...})
02

DarkMatter seals it outside your system

The record is stored in a vault that is independent of your infrastructure. No one inside your organization can modify it after it is committed.

03

Anyone can verify it, independently

Share a link or export a proof bundle. Regulators, auditors, and counterparties can check the record themselves, without a DarkMatter account, without coming to you.

Works with your stack

DarkMatter works with the tools you already use. One line drops into any Python or TypeScript agent.

Python SDKAvailable
TypeScript SDKAvailable
REST APIAvailable
LangGraphAvailable
Anthropic SDKSoon
OpenAI SDKSoon
LangChainSoon
CrewAISoon
AWS BedrockSoon
Self-hostSoon
Read the SDK docs →
Why it works
01

Independent of your system

The vault exists outside your infrastructure. DarkMatter stores the record, but verifying it needs nothing from us. Export a bundle and you hold your own copy of the hashes, so any later change on our side fails against it.

02

You can hold the keys

At L3 a record is signed with a key only you hold, before it reaches us, so we could not have produced it on your behalf. Export a chain at any level and it verifies offline against the open-source verifier, with no call back to us.

03

No vendor dependency to verify

Export a record and anyone can check it without a DarkMatter account, without internet access, and without trusting us. The verifier is open source and runs locally against the bundle you hold.

Records for controls and audits

Not a control. Not an auditor. A record an assessor can re-check.

Six frontier companies signed the voluntary White House Accord on Super Intelligence on 29 September 2026. It asks each of them for four layers of controls and audits on their own models. DarkMatter is not a signatory and performs none of the four; this is what it does beside each one.

Layer
What the accord asks of a signatory
What DarkMatter does beside it
01

Internal controls

The accord asksEach company monitors the capabilities and alignment of its own models in training and deployment, in areas like cyber, biological and chemical threats, and ensures they do not hack or access technical systems in unintended ways.
DarkMatterNot this layer. DarkMatter does not monitor, evaluate, block or stop a model or an agent; it is where a control or an agent runtime writes what happened, and it holds only what is sent to it.
02

Internal team

The accord asksAn internal team confirms that the controls, monitoring and detection operate as intended and that issues are remediated.
DarkMatterThere is no API route to edit a committed record, and a request to delete one returns 405; deleting the whole account removes its records. A remediation record can name the issue record as its parent, with the parent's hash folded into its own; that shows the link was recorded, not that the fix worked.
03

External auditor or evaluator

The accord asksAn independent outside auditor or evaluator assesses whether the controls, monitoring and detection operate as intended.
DarkMatterDarkMatter is not that auditor. A record the owner shares downloads as a file in an open format with a CC0 specification, which an assessor can keep and check offline with an open-source verifier; it checks payload hashes and chain links, not signatures or checkpoints.
04

Board committee

The accord asksAn independent committee of the board oversees and receives reports from the control teams and from the internal and external auditors and evaluators, and sees that issues are remediated.
DarkMatterDarkMatter writes no board report. A shared record opens in a browser with no account and offers its proof file, so a link in a report someone else wrote can be opened and checked by a committee member or their adviser.

What this is not

DarkMatter is not a signatory to the accord, is not endorsed by or affiliated with any party to it, and is not a model developer or an auditor. The accord is voluntary and names no tool or evidence format, so nothing here is required by it.

DarkMatter records and does not stop anything, and a hash chain shows the records you were given still match their hashes, not that every action was recorded.

Record contents are kept for 30 days on the Free plan and one year on Pro; after that they may be removed while the hashes remain, so download the proof file while the contents are still in it.

No independent witness co-signs checkpoints today and the one registered witness is operated by DarkMatter, so detecting a change made by DarkMatter depends on you or your assessor holding a proof bundle exported beforehand.

The same kind of record is what our EU AI Act page discusses: Article 12 logging applies to stand-alone high-risk systems from 2 December 2027, and whether a system meets it is for you, your counsel and, where one is involved, a notified body to determine, not DarkMatter. DarkMatter holds no third-party certification today.

Get started today

The vault your AI agents needbefore they need it.

Set up in minutes. One line of code. Free to start. No card required.

Demo Docs Pricing Integrity Sign in Try it free