BLACKBOX IN ACTION

See the chain seal.
Live. Provable. Unalterable.

In under eight minutes: record an agent run from genesis to seal, trigger a fault, watch the policy engine catch and contain it on-record, then replay the tamper-evident chain and produce a regulator-ready audit certificate — all without trusting BLACKBOX itself.

FULL DEEP DIVE · 25 MIN LISTEN
▣
DEEP DIVE EPISODE
The Cryptographic Flight Recorder for AI
BLACKBOX·—·Loading…
0:00−0:00
SYSTEM ARCHITECTURE

BLACKBOX: The Flight Recorder for AI Agents

The full system — anatomy of a sealed run, cryptographic proof, governance stakeholders, and audit features — in one view.

BLACKBOX · System Architecture · Infographic↓ Download
BLACKBOX: The Flight Recorder for AI Agents — system architecture infographic
Anatomy of a Sealed RunCryptographic ProofAccountability StakeholdersGovernance & Audit FeaturesClick to open full size ↗
Genesis → Seal
System prompt, tools, model snapshot, sampling params captured before a single token generates.
SHA-256 chain
hash(n) = SHA-256(hash(n−1) + canonical_JSON(event)). Post-hoc alteration breaks the chain permanently.
Zero-trust verify
Raw events + stdlib sha256 only. No BLACKBOX infrastructure required to verify a run.
Daily Merkle root
Every 24h all chain heads aggregate into one root. log(n) inclusion proof for any run at any timestamp.
LIVE DEMO

Every screen. Live from production.

Real data. Real runs. Captured from promptblackbox.com — not mockups.

promptblackbox.com/dashboard
MONITOR
BLACKBOX Dashboard — Recorded runs at a glance
MONITOR
Dashboard
Recorded runs at a glance
Every agent run listed append-only. Chain status, fault count, cost, model — visible at a glance. Click any run to enter the Replay Theater.
▣promptblackbox.com · BLACKBOX — flight recorder for AI agents
CHAPTERS
0:00The problem: AI agents with no audit trail
1:12Recording a run — genesis to seal
2:45The hash chain: why altering one byte breaks everything
4:03Fault detection and policy engine in action
5:30Replay Theater — verbatim playback, chain verified
7:10The examination report a regulator actually wants to see
WHAT YOU ARE WATCHING

Four guarantees, demonstrated live.

01
SHA-256 chain
Every event commits to every prior event. Alter one byte — downstream hashes break. Detectable, permanently.
02
Append-only
There is no UPDATE or DELETE endpoint for events. Not a policy — enforced at the schema level.
03
Merkle anchored
Daily tree of all chain heads. Any run can prove it existed before the anchor with a log(n) inclusion proof.
04
Provider neutral
Aligned to OpenTelemetry GenAI conventions. Claude, GPT-4o, Gemini, internal models — one schema.
"The aviation black box doesn't make planes safer by itself. It makes crashes survivable as information.BLACKBOX does the same for AI agents."
— BLACKBOX product thesis
THE INVARIANT
hash(n) = SHA-256( hash(n−1) + canonical_JSON(event(n)) )
GENESIS
00·0b61c7
→
REASONING
01·1c72d8
→
TOOL_CALL
02·2d83e9
→
FAULT
03·3e94fa
→
OUTPUT
04·4fa50b
→
SEAL
05·50b61c

Each node commits to every node before it. The FAULT event is sealed into the chain — not quietly removed. The SEAL event closes the run. Any post-hoc alteration to any event breaks the chain from that point forward, verifiable with stdlib sha256 alone.

READY TO RECORD

Your agents are running.
Start recording them now.

Two lines of Python. Zero infrastructure changes. The first run is free.

pip install blackbox-sdk

import blackbox_sdk as bb
bb.configure(api_url="https://your-blackbox.railway.app")
bb.instrument()  # every LLM call now recorded automatically
Record your first run →Read the full story
sha256 · append-only · Merkle-anchored · regulator-ready