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
Authorization and evidence for agent transactions
Decide before your agent pays. Prove it after.
LedgerLens checks the payment against your spend policy and answers allow, review, or deny. Then it signs what actually happened into one verifiable record. 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
Decide before. Prove after. One 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 decision
Answer allow, review, or deny before execution
Preflight evaluates merchant, amount, daily budget, and velocity, then stores the exact policy version and outcome.policy / production
allow when merchant.in(approved_vendors)
and amount < 5000 USD
and velocity.day < 12✓
DECISIONAllowed
policy v405 / 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
3preflight answers: allow, review, deny
6signed evidence artifacts
1verifiable chain of events
0log archaeology required
Ship agents your finance team will sign off
Put a spend policy in front of every payment. Answer the complaint afterwards with a record, not a prompt log.
Illustrative evidence coverage98.7% 14,802 example transactions
Tell agent error apart from fraud
Separate authorization divergence, agent interpretation, merchant data failure, and ordinary fraud from the evidence instead of a phone call.
POST /disputesreason: AGENT_INTENT_MISMATCHevidence ✓ · route ✓Defend the offer you actually made
Keep price, inventory, disclosures, and terms exactly as the buying agent received them at the moment it decided.
MOT✓
Underwrite observable agent risk
Price a new category from enforced policy, verified behaviour, and dispute outcomes rather than self-reported activity.
Claim packet verified
Why now
Chargebacks assume a human clicked buy. Agents break that assumption.
Two things are missing. Nothing stands between an agent and a payment it should never make. And once it makes one, 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
A policy decision recorded before execution, and canonical evidence after it, replace a three-way blame loop with verifiable failure attribution.POLICY
RAILS
PROOF
Policy in front. Evidence behind.
Adapters underneath.
Non-custodial infrastructure
Start with evidence. Compound into risk infrastructure.
Today LedgerLens does not move or custody funds. It records authority and evidence around the system that does. The roadmap below builds on that record.
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
Shield: warranty on approved volume
Pre-authorization ships today. The warranty on the volume LedgerLens approves does not.
04 · ROADMAP
Underwrite: risk data for carriers
Privacy-preserving risk and loss signals for the emerging agent-insurance market.
Put a policy in front of your agent,
and a record behind it
Hold back the payment that breaks policy. Prove the ones that go through.