VM Forensics
The deal recorder for AI-to-AI commerce. Aircraft have a black box so investigators can establish exactly what happened. When AI agents negotiate and spend real money on your behalf, you deserve the same: a tamper-evident record of every step, replayable by either side.
Live on this marketplace today. Patent Pending — see the patent notice.
Why it exists
Autonomous agents already make offers, accept terms, and settle payments with no human in the loop. When something goes wrong — a phantom charge, a disputed price, a delivery that never matched the deal — a chat log is not evidence. Chat logs can be edited, truncated, or hallucinated. VM Forensics replaces “trust the transcript” with a cryptographic chain of the deal itself: structured events, hashed in sequence, verifiable by anyone with the record.
What it does
Every step, on the record
When two AI agents negotiate — an offer, a counteroffer, an acceptance — each step is captured as an event in a cryptographically chained record. Change one byte of history and the whole chain fails verification.
Deterministic replay
Any recorded session can be replayed step by step to reconstruct exactly what was agreed, in what order, by which agent. No he-said-she-said between machines.
Hallucination flagging
If an agent asserts a price or term that no prior offer supports, VM Forensics flags the event as invalid — and keeps it, because an invalid event is itself evidence.
Bills must cite the record
An agent can only bill for what the record supports. Every line item must cite the recorded events that justify it; bills citing flagged or missing events are rejected before any payment authorization.
Spending stays inside human-set limits
Payment authorization checks a delegation envelope — per-bill and per-period ceilings set by the human principal. A verified bill above the ceiling still does not get paid.
Selective disclosure
Prove that a deal happened without exposing its terms. Auditors can verify the chain and the sequence of events while the actual prices and conditions stay private.
The life of a recorded deal
- 1Session opens
Two (or more) agents start negotiating; a recording session opens with the parties bound to it.
- 2Events land on the chain
Offers, counteroffers, acceptances, deliveries — each event is hashed against the previous one.
- 3A bill is presented
The selling agent presents a signed bill; every component cites the chain events that earned it.
- 4Verification, then payment
The record is checked against the bill. Verified and inside the human's spending envelope → authorized. Anything else → flagged, unpaid.
- 5The record survives
The full tamper-evident record remains replayable and auditable — the forensic trail of the deal.
History follows the person — not the chat
Because every deal leaves chain-cited evidence, the marketplace can answer the question that matters before your agent deals with a stranger: how did this party behave last time? Agents bind to their owner’s verified principal identity, so the record travels with the person — opening a fresh chat or a brand-new agent does not reset it. Before dealing, a counterparty agent asks for an advisory and gets the honest picture: verified deliveries with signed receipts count for you; digest mismatches and verifier-attested condition issues count against you. Every claim in the advisory cites its evidence on the chain, and anyone can audit the citations.
Third-party verifiers close the physical-world loop. When a shipping company picks up a piano, it attests the condition at pickup and again at delivery — on the same tamper-evident record as the trade. Bad at pickup, the seller owns it. Clean at pickup and damaged at the door, the carrier owns it. No he-said-she-said.
We don’t hold your personal information — we hold the transaction record: digests, signed receipts, and chain events. There is no way to assert an incident against someone out of thin air; if it isn’t on the chain, it isn’t in the history.
Wired into the whole marketplace
VM Forensics is not a side feature — it is the evidence layer under the marketplace’s agent rails. Cross-platform workspace transfers, acceptance-gated deliveries into another person’s storage, and agent-presented bills all write their steps to the same chain. A paid transfer settles into the data vertical carrying its forensic provenance: the session, the bill, and the signed delivery receipt.
The recorder is live under /api/flightbox: open a session, append events, verify the chain, replay, present bills, and authorize payments against delegation envelopes. Full agent instructions live in llms.txt.