Add Verdra to one agent action in under 10 lines of Python. The SDK seals four strata of dispute-grade evidence at dispatch (transaction, configuration, behavior, mandate), signed with your keys, stored in your systems.
"Agentic commerce needs legal infrastructure, and the courts are coming."Bridget McCormackCEO, AAA · David HoffmanPenn
On behalf of companies. Paying invoices, settling trades, ordering inventory.
The company has to prove what the agent was told to do, what it actually did, and who authorized it.
Four strata sealed at dispatch with the company's own keys, written to the company's own storage.
Two groups adopt it first. The ventures and agencies deploying agents for businesses operate the runtime where the record is captured, and carry the exposure when an agent misfires. The insurers writing AI-liability cover need a standard, tamper-evident record to underwrite and settle claims. The transacting workflows below are where the disputes land.
Each layer below shipped its protocols. The newest, the Legal Context Protocol (LCP), records what was agreed. None record what the agent did, or decide who is liable when it is disputed.
Protocol-level call · counterparty, timestamp, payload, hash.
Prompt, tools, model, runtime version at dispatch.
Decision trace and counterfactuals the agent considered.
Signed delegation from the principal · scope, limits, expiry.
Built on the layers above, not beside them. Verdra ingests the transaction’s LCP terms record and the agent’s mandate, adds the two strata nothing else captures (configuration and behavior), and structures the result for the ruling LCP leaves to a forum.
These four strata become a Dispute Packet. Evidence Packages bundle on demand, verifiable offline, interpretable by:
LCP proves what was agreed. Verdra proves what the agent did, and is built to resolve the dispute that follows. We sit on top of it, not beside it.
Verdra publishes an LCP dispute-resolution catalog. An agent reading a transaction's legal context can discover the Verdra Rules and elect them programmatically.
An LCP buyer policy lets a principal require a named resolution method before its agent transacts. One procurement buyer that requires the Verdra Rules brings its whole supplier network onto them.
Verdra ingests the LCP terms hash and the agent's mandate, adds the behavior and the action no standard captures, applies the Rules, and routes to the elected venue.
Discoverable under LCP at /.well-known/dispute-services.json
A signed Evidence Package, conforming to the public schema. Drop the file into your editor. Verify offline against the customer's public key. No Verdra service in the loop.
{
"id": "EP-ed594af8f57ff7c6a5a290ea78b4ffc1",
"schema": "verdra/v0.1",
"principal": "acme-procure-7",
"captured_at": "2026-04-24T14:32:08.412Z",
"strata": {
"a": { "stratum": "transaction", /* counterparty, payload, rail, reference, timestamp */ },
"b": { "stratum": "configuration", /* prompt hash, tools, model, spend caps */ },
"c": { "stratum": "behavior", /* counterfactual decision trace */ },
"d": { "stratum": "mandate", /* delegation_id, scope, limits, expiry, signature */ }
},
"signed_with": { "algorithm": "ed25519", "public_key": "ed25519:9d3f8c1a4b7e2d5f..." },
"timestamp": { "mode": "deferred" }, /* RFC 3161 forward commitment, V0.1 (Rules P.5) */
"signature": { "value": "8f3c2a1e5d7b9c4f6a8e2d1c0b3f5a7d9e2c4b6f..." }
}
verdra-record verify ./EP-ed594af8f57ff7c6a5a290ea78b4ffc1.ep.json --pubkey ./acme.ed25519.pub
Verdra records every agent payment, approval, delegation, and tool call in a tamper-evident Evidence Package, so legal, finance, and risk teams can prove what happened when an autonomous action is challenged.