01 / Authorization
Preserve exactly what the user authorized
A signed, versioned record of the principal, agent, scope, limits, expiry, and approval context.AG
VERIFIED AGENTOps Procurement 07DID · did:ledgerlens:7f21...84cCredential valid
Universal evidence and recourse for agent transactions
Every agent transaction gets a verifiable record
One evidence and recourse layer for every transaction an AI agent initiates—card, bank, procurement, checkout, or machine payment.
app.ledgerlens.dev
Evidence ledgerIllustrative data
Example captured volume$8,412,59098.7% complete
Example packets14,8026 rail labels
Verified transaction evidence
00:0012:00Now
CardsBankPOx402ACP
A
Procurement Agentag_01J9M8
ReviewDispute evidence
$4,280.00VendorNorthstar Compute
✓
Packet complete6 artifacts · signature valid
CardsBank transfersProcurementInternal ledgersACP checkoutAP2 / TAPx402MPP / UCPInsurance claims
One evidence model. Every rail.
Reconstruct what happened without the finger-pointing
02 / Intent
Record what the agent actually attempted
Normalize the requested purchase, reasoning inputs, merchant, amount, and expected outcome.03 / Merchant offer
Capture the offer as the agent saw it
Hash price, inventory, terms, disclosures, and source data at the moment of decision.PAYMENT INTENT$1,284.50
Vector DB · Annual plan
Merchant verifiedReady
04 / Policy check
Prove which controls ran before execution
Store the exact policy version, evaluated facts, approvals, and deterministic outcome.policy / production
allow when merchant.in(approved_vendors)
and amount < 5000 USD
and velocity.day < 12✓
DECISIONAllowed
21ms05 / Execution
Bind authorization to the payment event
Connect evidence to card, bank, procurement, checkout, internal-ledger, and machine-payment identifiers.L
ACPAP2x402MPPTAP06 / Receipt
Create the canonical dispute record
One tamper-evident package of what was paid, when, to whom, under which authorization, and why.LedgerLens receiptVERIFIED
rcpt_01J9Q7AM4AgentProcurement 07
MerchantNorthstar Compute
Amount$4,280.00
6signed evidence artifacts
1verifiable chain of events
5live rail policy templates
0log archaeology required
Prove what your agent was asked to do
Resolve customer complaints without stitching together prompts, tool logs, vendor responses, and payments.
Illustrative evidence coverage98.7% 14,802 example transactions
Agent-native dispute workflows
Classify agent error, authorization divergence, merchant data failure, and ordinary fraud correctly.
POST /disputesreason: AGENT_INTENT_MISMATCHevidence ✓ · route ✓Defend the offer you actually made
Preserve price, inventory, disclosures, and terms exactly as the buying agent received them.
MOT✓
Underwrite observable agent risk
Turn verified behavior and dispute outcomes into the loss data needed to price a new category.
Claim packet verified
Why now
Chargebacks assume a human clicked buy. Agents break that assumption.
When software initiates the purchase, user authorization, agent interpretation, merchant data, platform controls, and payment execution can each fail independently. Existing dispute categories cannot reconstruct that chain.
Inspect a real evidence case3+
potentially responsible parties in one agent dispute
The party holding the canonical evidence can replace a three-way blame loop with verifiable failure attribution.POLICY
RAILS
PROOF
The Universal Evidence API.
Adapters underneath.
Non-custodial infrastructure
Start with evidence. Compound into risk infrastructure.
LedgerLens does not move or custody funds. It records authority and evidence around the system that does.
01
Per protected transaction
Capture, sign, retain, and verify the complete transaction evidence chain.
02
Per automated dispute
Classification, counterparty routing, evidence export, and settlement workflow.
03 · ROADMAP
Underwriting intelligence
Privacy-preserving risk and loss signals for the emerging agent-insurance market.
Every agent transaction gets
a flight recorder
Capture the evidence before something goes wrong. Resolve responsibility when it does.