For enterprises
Your agents buy and sell for you. Prove what they agreed to.
Buying and selling are opposite positions in the same transaction, so they have their own sections below. The same Agentic Transaction Record (ATR) answers both.
When your agents buy
Your agent just bought something. Do you know what you agreed to buy? Can you prove it?
01 · you are the buyer
You accept terms like these hundreds of times a day now, through agents, at machine speed. Do you know which ones you accepted? From whom?
When you clicked, you saw the box and you remembered. Your agent does not click, does not remember, and does not stop. The obligations are the same size either way.
01.0Four purchases
- A dataset$4.00
Your agent paid $4.00 for a dataset. The seller’s terms grant them a perpetual licence to every query you send and the right to publish aggregate results.
You now hold that obligation. When did you take it on?
no record
- A subscription$29
Your agent bought a month of an API at $29. The terms auto-renew annually after the first period and require 60 days’ notice to stop.
Which of your agents is allowed to commit you for a year?
no record
- A service call$0.02
Your agent spent $0.02 on an enrichment call and sent a customer email address to do it. The seller’s terms place the data controller obligations on you.
Can you show your counsel which sellers you accepted that from?
no record
- A dispute
A seller delivered something unusable and will not refund. Their terms specify arbitration in a jurisdiction you would never have agreed to, and a liability cap of the amount paid.
Did you agree to that venue, or did nobody check?
no record
Every one of these settled in under a second, for a trivial amount, and left behind an obligation that is not trivial at all. That asymmetry is the whole problem.
01.1Three questions, answered
Did you get the terms the seller advertised, or a different version?
The ATR hash they published and the document they served are two different things. If those disagree, something changed between the offer and your payment.
What you agreed to buy — the gate fetches the document the seller actually serves and recomputes its digest against the ATR hash they advertised. Source: @integraledger/terms README (opens in a new tab)
Did anything check before you paid?
Not written to a log afterwards. Refused beforehand, while saying no still costs you nothing.
That it was checked before you paid — the signer is a port the gate holds. On a decline it is never called. Structural, not something anyone has to remember. Source: @integraledger/terms README (opens in a new tab) · Source: lcp docs: the buyer gate (opens in a new tab)
Can you show someone else what you allowed your agents to accept?
That you can show it to someone — the exact ATR your agent compared, kept byte for byte, and the payment that carries its ATR hash. What your agents may accept is your own policy, applied before the key; the ATR shows what it let through. Source: @integraledger/terms README (opens in a new tab) · Source: LCP §4 (opens in a new tab)
→What becomes possible
- 01
Let agents transact with sellers nobody vetted
Approval moves from the counterparty to the transaction — and the approved-vendor list stops being the bottleneck.
- 02
Refuse a clause category, everywhere, at once
An arbitration waiver, an unlimited indemnity, a unilateral amendment right — stated once in your policy, and applied before any agent’s key, with every seller. Source: LCP §4.2 (opens in a new tab)
- 03
Answer to a third party
Not a log of what your agents did, but the exact ATRs they accepted, each tied to the payment that carried it. Source: @integraledger/terms README (opens in a new tab)
- 04
Delegate authority without surrendering it
Authorization protocols say who may act, and within what limits; the ATR says what was agreed within them. An agent inherits a shape of authority, not a blank cheque. Source: LCP §9 (opens in a new tab)
- 05
Escalate instead of guessing
Not every proposal is a yes or a no. A policy can hand the interesting ones to a person and let the rest run. Source: LCP §4.4 (opens in a new tab)
When your agents sell
Your agent accepted USDC using x402. Can you prove the terms and conditions for what you sold?
02 · you are the seller
Your lawyer wrote these. Can you prove which of them governed the sale your agent just made?
A price and a wallet address are not a contract. Every other sale your business makes carries the clauses above; the ones your agent makes settle in seconds, to a counterparty you have never met, and point at nothing.
02.0Four sales
- Market data · API$0.008
An agent you have never heard of called your pricing endpoint 4,180 times last month at $0.008 a call. Your terms say the data is for internal use and may not be redistributed. That is $33.44 of revenue and a redistribution clause.
Can you show the clause travelled with any of those 4,180 calls?
no record
- Inference · SaaS
An agent ran 2,900 completions through your model endpoint and sent customer records in the prompts. Your data-processing terms set what you may retain and for how long, and they were revised in June.
Which version governed the calls made in May?
no record
- Licensed content$0.25
A research agent pulled 140 full-text articles at $0.25 each. Your licence permits quotation, not reproduction, and forbids training use.
If those articles surface in a model, what do you point at?
no record
- Goods · merchant
A procurement agent bought 60 units at your volume price and had them shipped. Your terms set a 14-day return window and cap liability at the purchase price.
Can you prove the buyer’s agent was given those terms before it paid?
no record
In every one of these the payment is unambiguous — the amount, the asset, the wallet, the timestamp. It is the other half of the transaction that has nothing attached to it.
02.1Three questions, answered
Which version of your terms applied to that sale?
Terms pages get edited. A sale that points at a URL points at whatever is there now — not at what was there when the agent agreed.
Which version applied — your terms named by their own hash, assembled per transaction. Not a URL that resolves to whatever is there today; the bytes that were served when the agent agreed. Source: lcp docs: the ATR (opens in a new tab)
Can you show the buyer’s agent was given them?
Not that they exist somewhere on your site. That they travelled with this payment, in the challenge the agent parsed before it signed.
That the agent was given them — the reference travels in the challenge the agent parses before it signs. On EVM the full 32 bytes then ride the EIP-3009 nonce it signs. Source: lcp docs: x402 (opens in a new tab) · Source: lcp docs: rails (opens in a new tab)
Can someone who was not there check any of it?
A counterparty, an auditor, an adjudicator — working from the ATR and the chain, without asking you and without asking us.
That anyone can check — hash the ATR’s bytes, and read the ATR hash back from the payment and the chain, with public software. It never routes through us. Source: lcp docs: recovering H from the chain alone (opens in a new tab) · Source: LCP §12.2 (opens in a new tab)
→What becomes possible
- 01
Sell to an agent that has never met you
The terms arrive with the challenge and hash back to a document the buyer can fetch — the ATR, not the relationship, carries the trust.
- 02
Make the clause that protects you travel
Your liability cap, your warranty disclaimer and your acceptable-use limit only work on a sale that carried them. The payment is priced; the consequence is not.
- 03
Offer different terms to different buyers
Assembled per transaction, not per site. One page of static terms for everybody was a limitation of the web, not a law of commerce. Source: lcp docs: the ATR (opens in a new tab)
- 04
Resolve a disagreement from the ATR
Evidence produced at the moment of sale, not reconstructed from inboxes — a lookup rather than an argument.
- 05
Open the categories agents are locked out of
Where the agreement is the product. These are not waiting on faster payments. They are waiting on provable terms.
- 06
Your path to recourse is declared up front
At Level 4, your discovery document points to your dispute process, returns and contacts. The clause in your terms document is what governs. Source: LCP §3, Level 4 (opens in a new tab) · Source: LCP §2.5 (opens in a new tab)
Sources (7)
lcp docs: the ATR (opens in a new tab) · lcp docs: x402 (opens in a new tab) · lcp docs: rails (opens in a new tab) · lcp docs: recovering H from the chain alone (opens in a new tab) · LCP §12.2 (opens in a new tab) · LCP §3, Level 4 (opens in a new tab) · LCP §2.5 (opens in a new tab)
One transaction, both sides
The payment is priced. The consequence is not.
An agent books two nights at $240. The rate it took was the non-refundable one — $40 cheaper than the flexible rate on the same room. The trip moves by a day.
What they are holding
The traveller
A booking whose change and cancellation terms decided its price, and no record of which rate’s terms were accepted — or whether the flexible option was presented at all.
The hotel
A non-refundable policy that is the entire justification for the lower price, and no way to show the agent was given it before it booked.
The argument is never about whether the policy exists. It is about which one applied.
One ATR answers both: it holds the rate’s terms, and the payment for that booking carries its ATR hash. Source: lcp docs: the ATR (opens in a new tab)
Sources (1)
What the ATR does not decide
The ATR is a record, never a judge. That a terms acceptance was bound and evidenced is a technical fact; whether the resulting agreement is enforceable is not ours to assert.
Ready to see your own agreements proved?
Tell us what you sell, buy or carry, and we will show you where the agreement rides in it.
The hosted appliance is free on test networks, with test-network USDC.