Skip to main content
AI agent evidence

Proof of what your AI agents did, and what they were allowed to do.

Signed, offline-verifiable evidence for every agent decision, from mandate to receipt. Hand your auditor a Case File. They check it with our public key set and an open-source verifier, not with our word.

Logs are not evidence.

Every tool in your stack answers a different question. Only one answers it in a form someone else can check.

Identity vendors: who is this agent?

Governance platforms: what should happen?

Observability and gateway vendors: what was logged, by them?

AI Identity: prove it. Signed records your auditor verifies offline, without trusting us.

The Case File

One download holds the forensic report, the signed checkpoints that anchor its events, and the verifier. A signed manifest lists every file with its SHA-256 hash, so a change to any file after issue is detectable.

  • ✓Public check: anyone with our public key set confirms every file is what we issued, and that each anchored event sits under a signed Merkle checkpoint.
  • ✓Key-holder check: your organization's verification key recomputes every event hash in chained order. Nothing inserted, deleted or changed.
  • ✓Witness check (optional, online): the checkpoints match our public feed and its independent mirror.
  • ✓Pruned rows are accounted for by tombstones. A gap without one is rejected.
  • ✓Includes a plain-English reliability statement written to support FRE 702 and ISO/IEC 27037 documentation.
python3 ai_identity_verify.py bundle case-file.zip --jwks jwks.json

Proof primitives

Each one is a file or a signature you can check yourself.

Hash-chained audit trail

Every gateway decision, allow or deny, is an HMAC-SHA256 chained record tied to the agent, its key and the policy that ruled. Alter or remove one record and the chain breaks at that point.

Signed session attestations

Sign any session as a DSSE envelope with an ECDSA P-256 key held in Google Cloud KMS. The payload commits to the exact audit range and the chain hash at sign time.

Evidence Anchor

Every 15 minutes, new events are committed to a signed Merkle checkpoint, published on a public feed and mirrored off our infrastructure. Prove one event is in the record without revealing any other.

Open verifier

A single-file Python CLI checks Case Files, attestations, inclusion proofs and chains offline. Chain checks need only the standard library.

OCSF 1.9.0 output

Export events as OCSF NDJSON carrying the attestation object and record_integrity profile we contributed to OCSF 1.9.0.

AID-EMIT-1 and edge ingest

Enforcement points you run emit signed records to an open spec. We verify each on arrival and quarantine failures with the reason.

Incident reconstruction

Pick an agent and a time window. Reconstruct every decision in order, with the policy that was active and a chain check over the range. Export the same window as a Case File, JSON with a chain-of-custody certificate, or CSV.

Custody

Choose how much each agent records and how long you keep it. Pruned rows leave tombstone receipts in the chain, legal holds freeze records, and erasing captured content takes two people. Retention, holds and erasure are set up with you during onboarding.

See custody controls →

The Four Pillars of AI Agent Evidence

Identity vendors answer who. Governance platforms answer what should happen. Logging and gateway vendors answer what they recorded. AI Identity answers prove it, with evidence that verifies without trusting us.

PillarCore QuestionAI Identity Capability
ForensicsWhat happened, provably?Signed Case Files, DSSE session attestations and public Evidence Anchor checkpoints, checked offline with the open-source verifier.
PolicyWhat was it allowed to do?Signed mandates with spend ceilings and validity windows, a fail-closed gateway, and a signed receipt for each draw, allowed or denied.
ComplianceWas the record kept properly?Retention policies, legal holds, tombstone receipts for pruned records, and redaction receipts for two-person erasure. Export profiles for SOC 2, EU AI Act and NIST AI RMF.
IdentityWhich agent did it?A key per agent, rotation without downtime, revocation and shadow-agent detection, so every record names the agent that acted.

Where the evidence maps

Mappings to the frameworks we export profiles for. Your auditor decides what they satisfy.

EU AI Act

Record-keeping (Art. 12)

Hash-chained trail with per-decision metadata, retention policies with tombstone receipts, Case File export.

SOC 2 (aligned, no audit yet)

Tamper-evident logging

DSSE-signed attestations over an HMAC-SHA256 chain. Signing keys in Google Cloud KMS, chain keys in the application tier, so forging evidence needs both.

NIST AI RMF

MANAGE 4.3, MEASURE 2.8

Incident reconstruction, signed export profiles, offline verification.

Logs ask to be believed. Evidence can be checked.

Start free with 5 agents and a hash-chained audit trail. Case File export and session attestations are included on every plan.