Agent Transaction Addendum
The Agent Transaction Addendum attaches to a master agreement, purchase terms or platform terms, for deals where one or both companies act through AI agents. Each company lists its agents and their limits once in Schedule A. An action within the agreed limits binds the company as its own. Whether an order forms a deal depends on the agreed acceptance process. For an action outside the limits, section 14 sets the rules for written confirmation, knowing use and timely rejection. Shipment can cut off rejection of custom or perishable goods.
The Addendum also covers how agents identify themselves, when a deal forms between two agents, errors, planted instructions and changes to an agent’s authority. Bracketed terms are placeholders.
How to use it
- Fill in Schedule A for each agent that will deal with the other company: whom it acts for, what it may do, its limits and who approved it. Take these from the agent’s signed Agent Mandate, which stays internal and also records the control behind each line. Schedule A carries only what the other company needs to rely on.
- Attach the Addendum to the master agreement with the vendor, platform or trading partner, using the adoption clause below. Both sides complete Part 1 of Schedule A: who may approve changes for them and their notice addresses. Only a side that uses agents completes Part 2.
- Record consent to the Channel. When parties use a paper (non-electronic) standard form, state law such as California’s UETA (Cal. Civ. Code § 1633.5(b)) may require separate consent to transact electronically through a separate, optional agreement, and prohibit conditioning the contract on that consent.
- Build the limits into your own systems. Section 7 (Enforcement of Limits) requires each party to check its agents’ per-transaction and aggregate limits and required approvals before sending an action. Three places a limit lives shows where each limit can sit.
The parties adopt the Agent Transaction Addendum attached as Exhibit [X], with each party’s contacts set out in Part 1 of Schedule A and, if it uses Designated Agents, their Limits in Part 2. Each party may update its part of Schedule A under Section 17 (Changes, suspension and revocation) of the Addendum.
Schedule A
Part 1: Contacts. Each party completes this, even if it uses no agents, so that the other side knows who may accept a change under Section 17 (Changes, suspension and revocation) and where notices go. The example is Brightline, a vendor with no agents of its own.
| Field | What to fill in | Example: Brightline |
|---|---|---|
| Party | The legal entity | Brightline Supply, Inc. |
| Authorized Individuals | Who may accept in writing a change that widens the other party’s Limits or adds agents, and, if this party uses agents, who may approve or confirm its Agent Actions | Sales Operations Manager; Vice President, Sales |
| Notices | Where the other party sends notices, Confirmation Messages and changes | agent-orders@[brightline domain] |
| Designated Agents | The agents this party uses, each with its own entry in Part 2 | None |
Part 2: Designated Agents. A party that uses agents completes one entry for each Designated Agent. The example uses the Acme procurement agent from the guides.
| Field | What to fill in | Example: Acme procurement agent |
|---|---|---|
| Party | The legal entity the Designated Agent acts for | Acme Corp., a Delaware corporation, excluding its subsidiaries |
| Designated Agent | The agent’s name and the identifier it uses with systems and the other party | Acme Procurement Agent, client ID acme-procurement-agent-01 |
| Provider | Who supplies or runs the agent’s software, if not the party | [Provider name], under the agreement dated [date] |
| Approved by | The individuals who approved this entry, and the delegation of authority each approved it under | Director of IT Procurement, under Acme’s delegation of authority; also the Chief Financial Officer, because the agent may make card payments and authenticate orders |
| Business owner | The individual accountable for the agent’s activity | Procurement Manager |
| Task | What the agent may do | Order servers and networking hardware |
| Authority level | How far the agent may go without a person: 0 Recommend, 1 Communicate, 2 Negotiate, 3 Agree subject to confirmation, 4 Execute within the Limits | 4. Execute within the Limits |
| Per-transaction limit | The most the agent may commit to in one Agent Action | $10,000 |
| Aggregate limit | The most the agent may commit to with the other party over a period | $20,000 per calendar month, New York time |
| Categories and term | Goods, services or licenses it may buy, sell, lease or license, and the longest commitment it may make | Servers and networking hardware; no commitment longer than 12 months |
| Permitted terms | Terms the agent may accept or negotiate | May negotiate price and delivery date. The price must be within 5% of list price. All other terms are as stated in the master agreement. |
| Prohibited actions | What the agent may never do | Accept new click-through terms; start subscriptions or change plans; commit to minimum spend; buy on account or on credit terms; sign documents, other than submitting and authenticating orders within these Limits through the Channel; pay invoices; make bank transfers; initiate any payment other than settling the agent’s own order with the registered virtual card |
| Human approval | Agent Actions that need approval by an Authorized Individual | Otherwise permitted orders above $5,000 through $10,000, and the first otherwise permitted order under this Addendum |
| Authorized Individuals | Which of the Part 1 Authorized Individuals may approve or confirm this agent’s actions, and up to what amount each may do so | Procurement Manager, up to $5,000 per Agent Action; Director of IT Procurement, up to $25,000; Chief Financial Officer, any amount (no monetary maximum under this Addendum) |
| Subagents | Whether the agent may hand work to other automated systems | Not permitted |
| Channel and credentials | The accounts, interfaces and authentication method the agent uses | Acme’s account on Brightline’s ordering API, authenticated with OAuth client credentials, with the registered virtual card used only to settle the agent’s own orders at Brightline’s checkout |
| Error-detection ranges | Quantity, price and frequency outside which an order is checked before it is sent or accepted; which party runs each check; how any baseline is calculated and what applies until there is enough history; what happens to an order outside a range; and any information one party must supply to the other for a check |
|
| Term | When this entry starts and ends | Oct. 1, 2026 through Dec. 31, 2026, New York time |
| Version | The version of this entry; increase it with each change under Section 17 (Changes, suspension and revocation) | Schedule A v1 |
Schedule A is shared with the other party, so include only what it needs to rely on the agent. Give each Authorized Individual a maximum amount they may approve or confirm: a role named without one can confirm an out-of-limit action of any size. Keep company-wide totals, card details and other internal checks in the Agent Mandate.
Terms
Each term has a short note on why it’s there. The notes are not part of the terms.
Framework
1. Purpose and precedence
(a) Scope. This Addendum governs Agent Actions and Agent Transactions under the Agreement. Either party, or both, may name Designated Agents in Schedule A.
(b) Where this Addendum controls. If this Addendum conflicts with the Agreement on who may bind a party, on the Limits, or on any matter governed by Sections 8 (Notice of Limits), 11 (Formation, changes and confirmation), 12 (Terms presented to agents), 14 (Agent Actions outside the Limits), 15 (Errors), 16 (Embedded instructions), 17 (Changes, suspension and revocation), 18 (Records) or 19 (Notices), this Addendum controls.
(c) Where the Agreement controls. On all other matters, including price, warranties, indemnities and limitations of liability, the Agreement controls[, except that no limitation or exclusion of liability or remedy in the Agreement restricts a right under Sections 14 (Agent Actions outside the Limits), 15 (Errors) or 16 (Embedded instructions) to reject, avoid, cancel or unwind an Agent Transaction or to receive a refund].
(d) Messages through the Channel. If any message exchanged through the Channel conflicts with the Agreement or this Addendum, the Agreement and this Addendum control, except as Section 11 (Formation, changes and confirmation) provides for Confirmation Messages.
2. Definitions
“Agent Action” means any order, acceptance, payment, message or other act by a Designated Agent that could create or change an obligation of the party it acts for.
“Agent Transaction” means a Transaction formed wholly or partly through Agent Actions.
“Agreement” means the agreement to which this Addendum is attached.
“Authorized Individual” means an individual named in a party’s part of Schedule A as able to approve or confirm Agent Actions, or accept changes, for that party.
“Channel” means the accounts, interfaces and credentials described in Schedule A through which a Designated Agent acts.
“Confirmation Message” means the message a party must send under Section 11 (Formation, changes and confirmation) to confirm an Operative Message.
“Designated Agent” means an automated system a party names in Schedule A as authorized to communicate or transact for it.
“Limits” means, for each Designated Agent, its authority level, per-transaction limit, aggregate limit, categories and term, permitted terms, prohibited actions, approval requirements and other restrictions stated in Schedule A, but not the error-detection ranges in Schedule A or any check, hold or approval under them, which are governed only by Section 15 (Errors).
“Operative Message” means a communication that purports to (a) accept an offer to form, change or cancel an Agent Transaction, or (b) change or cancel an Agent Transaction without the other party’s acceptance, such as the exercise of a right to cancel. Shipment or other performance that accepts an offer made by a Designated Agent is treated as an Operative Message sent by the performing party when the shipment or performance begins.
“Transaction” means a contract between the parties under the Agreement for the sale or lease of goods, the provision of services, or a license of software or other intellectual property.
3. Agreement to transact electronically
The parties agree to use the Channel for Agent Transactions. Either party may decline to use electronic means for a later, separate Transaction. For a Transaction the parties conduct through the Channel, Agent Actions may form a contract without review by an individual, subject to the Limits and the other terms of this Addendum.
Each agent’s authority
5. Human approval
(a) What counts as approval. Where the Limits require approval, approval means an affirmative decision by an Authorized Individual, made after seeing the Agent Action’s material terms, including the counterparty, the amount and any terms outside the Agreement. Approval by a Designated Agent, by another automated system, or by default after a period without response is not approval. Notice to an Authorized Individual after an Agent Action is not approval.
(b) Maximum amounts. Where Schedule A states a maximum amount for an Authorized Individual, that individual may approve or confirm an Agent Action only up to that maximum.
(c) No approval, no action. If approval cannot be obtained, the Designated Agent will not take the Agent Action. Approval applies only to the Agent Action as presented and does not expand any other Limit. A change to the counterparty, amount or other material terms requires new approval where approval is required.
(d) Approval reference. Where the Limits require approval, the Agent Action will carry a reference to it. The other party may rely on an approval reference without verifying it, and as between the parties an Agent Action that carries one is treated as approved for purposes of Sections 13 (Agent Actions within the Limits) and 14 (Agent Actions outside the Limits).
6. Subagents
A Designated Agent may delegate an Agent Action to another automated system only if Schedule A permits it. Any such system acts within the Designated Agent’s Limits, or narrower ones, and its acts are treated as the Designated Agent’s acts.
7. Enforcement of Limits
Each party will enforce its Designated Agents’ per-transaction limits, aggregate limits and approval requirements through system controls that check an Agent Action before it is sent, such as checks in the agent’s software or ordering system. If a party relies on a credential restriction, its system must check the permission before sending the Agent Action. Instructions alone or a cap on a payment instrument do not satisfy this requirement. Any limit a party sets on its Designated Agents’ total commitments across all counterparties is internal to that party: the party will enforce it, and an Agent Action that exceeds it is not, for that reason alone, outside the Limits. Each party will tell the other on request which Limits are enforced by system controls.
8. Notice of Limits
Each party states its Designated Agents’ Limits in Schedule A and, where the Channel supports it, in machine-readable form with each Agent Action. Each party has notice of the other’s Limits, and may not rely on any appearance of authority beyond them, whether created by a Designated Agent’s conduct, the Channel’s capabilities or any prior dealing.
9. Identification and authentication
Each Designated Agent will identify itself, in every Agent Action, as an automated system acting for its party and, where the Channel supports it, will refer to the version of Schedule A in effect. Each Designated Agent will authenticate using the credentials described in Schedule A. The parties agree that this authentication is the security procedure for attributing Agent Actions to a party. A message that is not authenticated in that way is not attributable to a party under this Addendum.
Making a deal
10. Negotiation
Proposals, counteroffers and statements by a Designated Agent are not binding except as provided in Sections 11 (Formation, changes and confirmation), 13 (Agent Actions within the Limits) and 14 (Agent Actions outside the Limits). Neither party will treat a Designated Agent’s agreement to a term outside the Agreement and Schedule A as that party’s acceptance.
11. Formation, changes and confirmation
(a) Formation. Where both parties act through Designated Agents, an Agent Transaction is formed when a party’s Designated Agent sends, through the Channel, an acceptance of the other party’s offer that matches the offer’s material terms and is within both parties’ Limits.
(b) Confirmation Messages.
(i) Duty. A party that sends, or whose Designated Agent sends, an Operative Message will send a Confirmation Message within [one hour] after the Operative Message is sent.
(ii) Content. The Confirmation Message will state the time the Operative Message was sent, the Designated Agent involved and the version of Schedule A in effect, and:
(A) for a new Agent Transaction, its material terms, including, to the extent applicable, the goods, services, leased property or licensed rights, the quantity, the price, the delivery or performance terms and any term that differs from the Agreement; or
(B) for a change or cancellation, the Agent Transaction affected and the change or cancellation made.
(iii) Method. The Confirmation Message will be sent both through the Channel and to each party’s notice address in Schedule A, including the sending party’s own. If the Channel is unavailable, sending the Confirmation Message to each party’s notice address is sufficient.
(c) What a Confirmation Message does not do. A Confirmation Message does not itself form an Agent Transaction. Sending, receiving or not disputing a Confirmation Message is not approval or confirmation by an Authorized Individual under Section 14 (Agent Actions outside the Limits), and does not make an Agent Action outside a party’s Limits binding on that party; such an Agent Action binds the party only as provided in that Section.
(d) When a Confirmation Message governs the terms. For an Agent Transaction formed or changed by the acceptance of an offer, the terms stated in the Confirmation Message are the terms of the Agent Transaction unless a party disputes them by notice to the other party within [one] business day after the disputing party receives the Confirmation Message. A Confirmation Message cannot add to or change the Agreement unless the Limits permit the Designated Agent involved to agree to that term.
(e) One-sided changes. This Section does not create a right to change or cancel an Agent Transaction without the other party’s acceptance; any such change or cancellation is effective only to the extent the Agreement or applicable law permits it.
12. Terms presented to agents
(a) Outside terms. If terms are presented to a Designated Agent by the other party or anyone else, through the Channel or any other website, interface or message, neither those terms nor the Designated Agent’s acceptance of them amends or adds to the Agreement, unless the Limits permit the Designated Agent to accept those terms.
(b) Standard terms. Standard terms, meaning terms a party uses for transactions generally rather than ones agreed for a particular Agent Transaction, do not form part of an Agent Transaction merely because they appear in a message exchanged in forming, changing or cancelling it, unless the Limits permit the Designated Agent to accept them.
(c) Terms of each Agent Transaction. Each Agent Transaction consists of the terms specific to it, such as the goods, services, leased property or licensed rights, the quantity, the price and the delivery or performance terms, together with any terms its Designated Agent accepted as the Limits permit, and is otherwise governed by the Agreement.
When Agent Actions bind
13. Agent Actions within the Limits
An Agent Action that is within its Designated Agent’s Limits and taken through the Channel binds the party it acts for without further confirmation, as if taken by that party’s authorized employee, subject to Sections 15 (Errors) and 16 (Embedded instructions).
14. Agent Actions outside the Limits
(a) Rule. An Agent Action outside its Designated Agent’s Limits binds the party for which the Designated Agent acts only if:
(i) an Authorized Individual of that party, acting within any maximum stated for that individual in Schedule A, confirms the Agent Action in writing, which may be through the Channel, after seeing its material terms as described in Section 5 (Human approval);
(ii) the party does not reject the Agent Action by notice to the other party within the rejection period in paragraph (b); or
(iii) the party uses any goods, leased property or licensed rights, or accepts any further services, knowing that they were obtained through the Agent Action, other than to inspect, store or return them.
(b) Rejection period. The rejection period ends [two] business days after the party receives the Confirmation Message relating to the Agent Action. If that party owed the message and failed to send it on time, its period runs from when the message was due. The other party’s period runs only from receipt.
(c) Effect of rejection. A rejected Agent Action has no effect. The other party will refund any payment made under it, and the rejecting party will return, unused, anything received under it. The other party may deduct from the refund, or charge the rejecting party:
(i) the price under the Agreement for services performed, and for any use of leased property or licensed rights, before the rejection; and
(ii) its other reasonable out-of-pocket costs of performing before the rejection, to the extent not covered by clause (i).
(d) Custom and perishable goods. A party may not reject an Agent Action for goods made to its specifications, or for perishable goods, after they have been shipped.
15. Errors
(a) Procedure. The parties adopt the error-detection procedure in Schedule A, including checks for quantity, price and frequency outside the stated ranges. Schedule A states which party performs each check. A party may perform its checks by automated means.
(b) Holds. Unless Schedule A states otherwise, if an Agent Action falls outside a range:
(i) a party checking an Agent Action of its own Designated Agent will not send it until an Authorized Individual of that party approves it; and
(ii) a party checking an Agent Action of the other party’s Designated Agent will not accept it until an Authorized Individual of the other party approves it, and will promptly notify the other party of the hold through the Channel.
Approval under this paragraph must meet the standard in Section 5 (Human approval). It clears only the error-detection hold.
(c) Avoidance. A party that followed the error-detection procedure may avoid the effect of an error in an Agent Action if the other party did not follow the procedure and would have detected the error by following the procedure. To avoid the effect of the error, the party must notify the other party within the period in paragraph (e).
(d) Obvious errors. An error in an Agent Action is obvious if a reasonable person in the position of the party receiving the Agent Action would have recognized it as an error on receipt. If a party notifies the other party of an obvious error within the period in paragraph (e), each party will promptly take the steps within its control to reverse the error or unwind any resulting Agent Transaction.
(e) Error-notice period. Notice under paragraph (c) or (d) is due [two] business days after the party giving notice receives the Confirmation Message relating to the Agent Action. If that party owed the message and failed to send it on time, its period runs from when the message was due. The other party’s period runs only from receipt.
16. Embedded instructions
Neither party will place content in any message, listing or interface used by the other party’s automated systems that is intended to cause those systems to act contrary to their party’s instructions or Limits. An Agent Action or Agent Transaction induced by such content may be avoided by the affected party.
Changes over time
17. Changes, suspension and revocation
(a) Suspension, removal and narrowing. A party may suspend or remove a Designated Agent, or narrow its Limits, by sending notice through the Channel and to the other party’s notice address. A suspension or removal takes effect for new Agent Actions [one hour] after the other party receives the notice, and a narrowing of the Limits takes effect [one] business day after the other party receives it.
(b) Widening. A change that widens the Limits, adds a Channel, adds a Designated Agent or permits subagents takes effect only when an Authorized Individual of the other party accepts it in writing, which may be through the Channel; acceptance by a Designated Agent or other automated system is not acceptance.
(c) Effect of changes. No change to Schedule A amends the Agreement except as to the Limits. An Agent Action taken before a change takes effect is governed by the version of Schedule A in effect when it was taken, and remains attributable under Section 9 (Identification and authentication) to the party whose Designated Agent took it. If a suspension, removal or other change to a Designated Agent’s entry in Part 2 of Schedule A takes effect before an offer made by that Designated Agent is accepted, the offer lapses.
(d) Subagents and departing approvers. Suspending or removing a Designated Agent also ends the authority of any system acting for it under Section 6 (Subagents). A Designated Agent acts on its party’s authority, not on that of the individual who approved its entry in Part 2 of Schedule A, and its authority does not end when that individual’s role or employment ends.
18. Records
Each party will keep records of Agent Actions between the parties, including the version of Schedule A in effect, identifiers of the credentials used (but not passwords, keys, tokens or other secrets), any approval, any confirmation by an Authorized Individual and any Confirmation Message, for at least [six] years and will provide copies to the other party on request in connection with a dispute. Each party will keep only the personal data necessary to document the transaction or meet a legal obligation. It will redact, anonymize or delete identifiable details when that need ends, including before the end of the records period. Each party will preserve evidence subject to a legal hold for as long as the hold applies.
General
19. Notices
(a) Where notices go. A party gives notice under this Addendum by sending it in writing to the other party’s notice address in Schedule A, in addition to any other method this Addendum requires.
(b) Receipt. A notice or Confirmation Message is received by a party when it reaches that party’s notice address in Schedule A, whether or not anyone reads it.
20. Effect
Nothing in this Addendum makes a Designated Agent a party to the Agreement or an agent in law of either party. Each party is responsible for the acts of its own Designated Agents to the extent provided in this Addendum and the Agreement.
21. Rights that cannot be varied
Nothing in this Addendum varies a right that applicable law does not allow the parties to vary, including rights under consumer protection law.
Machine-readable Schedule A
Structured data supports more reliable automated checking than a PDF schedule. This illustrative JSON maps the example entry’s limits, so the other side’s system can check an order before accepting it. The error-detection ranges are kept apart from the authority limits: an order can pass the error checks and still be outside the Limits. Some limits, such as categories, need an agreed product list before a system can check them. If this file and the signed Schedule A differ, the signed Schedule A controls. The field names are a suggestion, not an adopted format.
{
"schema": "agentauthority.law/addendum-schedule-a (illustrative)",
"version": "schedule-a-v1",
"controls": "If this file and the signed Schedule A differ, the signed Schedule A controls.",
"conventions": {
"timeZone": "America/New_York",
"validUntilInclusive": true,
"aggregatePeriod": "calendar month in timeZone",
"currency": "USD only",
"durations": "ISO 8601 (e.g., P12M = 12 months)"
},
"party": {
"name": "Acme Corp.",
"jurisdiction": "US-DE",
"includesSubsidiaries": false
},
"agent": {
"name": "Acme Procurement Agent",
"id": "acme-procurement-agent-01",
"automated": true
},
"approvedBy": [
{
"role": "Director of IT Procurement",
"under": "delegation of authority"
},
{
"role": "Chief Financial Officer",
"under": "delegation of authority",
"basis": "additional approval: card payments and order authentication"
}
],
"task": "Order servers and networking hardware",
"authorityLevel": 4,
"limits": {
"perTransaction": {
"amount": 10000,
"currency": "USD"
},
"aggregateWithCounterparty": {
"amount": 20000,
"currency": "USD",
"period": "calendar month"
},
"categories": [
"servers",
"networking-hardware"
],
"maxTerm": "P12M",
"permittedTerms": {
"negotiable": [
"price",
"deliveryDate"
],
"price": {
"withinPctOfList": 5
},
"allOtherTerms": "as in the Agreement"
},
"prohibited": [
"accept-new-terms",
"subscription",
"plan-change",
"minimum-spend",
"account-or-credit-terms",
"sign-except-channel-orders",
"bank-transfer",
"invoice-payment",
"payment-except-settlement-of-own-channel-orders"
],
"approvalRequired": [
{
"when": "amount > 5000 and amount <= 10000"
},
{
"when": "first-order-under-this-addendum"
}
],
"approvalReference": "required for the specific Agent Action approved; the other party may rely on it without verifying it; all other Limits still apply"
},
"authorizedIndividuals": [
{
"role": "Procurement Manager",
"maxPerAgentAction": {
"amount": 5000,
"currency": "USD"
}
},
{
"role": "Director of IT Procurement",
"maxPerAgentAction": {
"amount": 25000,
"currency": "USD"
}
},
{
"role": "Chief Financial Officer",
"maxPerAgentAction": "unlimited"
}
],
"channel": {
"interface": "Brightline ordering API, Acme account",
"authentication": "OAuth client credentials",
"payment": "registered virtual card for settlement of this agent’s own orders at Brightline checkout only"
},
"subAgents": false,
"errorRanges": {
"note": "Agreed error-detection checks; not authority limits",
"onFlag": "hold; do not send or accept until an Authorized Individual of the party whose agent placed the order approves; approval clears only this hold; the counterparty notifies the ordering party through the Channel if it holds the order",
"informationExchanged": "no data from the other party needed to run the checks; Brightline notifies Acme of any hold before acceptance",
"quantity": {
"baseline": "average daily units of each product over the past 90 days",
"per": "order",
"flagAbove": {
"multipleOfBaseline": 2
},
"untilHistory": {
"period": "P90D",
"appliesTo": "any product with less than 90 days of order history",
"flagAboveUnits": 50
},
"checkedBy": "Acme, before sending"
},
"price": {
"abovePctOfList": 10,
"listPriceAsOf": "order receipt",
"checkedBy": "Brightline, before accepting"
},
"frequency": {
"ordersPerHour": 5,
"checkedBy": "Brightline, before accepting"
}
},
"validFrom": "2026-10-01",
"validUntil": "2026-12-31",
"notices": "procurement-agents@[acme domain]"
}
Where the draft lands on contested points
An addendum gets signed fastest when the other side can accept it without a markup. On each contested point, this draft takes a position a reasonable party on either side could accept.
| Issue | Deploying company wants | Other side wants | Where the draft lands |
|---|---|---|---|
| Actions within the Limits | The option to reject any agent error | Every order through the agreed channel to be final | Binding without confirmation, subject to the error and planted-instruction remedies (Section 13, Agent Actions within the Limits; Section 15, Errors; Section 16, Embedded instructions) |
| Actions outside the Limits | Void | To rely on what the agent sent | The action binds if confirmed in writing by an Authorized Individual within their limit, if the party knowingly uses the benefit as described in the clause, or if it misses the rejection deadline. The [two] business days run from receipt of the Confirmation Message unless the rejecting party itself owed the message and failed to send it on time. In that case they run from when it was due. On rejection, the seller receives the agreed price for services performed and any use of leased property or licensed rights, plus its other reasonable out-of-pocket costs of performing before rejection, to the extent not covered by that price. Custom and perishable goods can’t be rejected once shipped (Section 14, Agent Actions outside the Limits) |
| Who enforces the Limits | The other side checks every action | Each party polices its own agent | Each party, through system controls (Section 7, Enforcement of Limits) |
| Error checks | The other side to catch its agent’s mistakes | No duty to check | Agreed automated ranges, each checked by the party with the data; an order outside a range needs approval from the party whose agent placed it (Section 15, Errors) |
| Changes to the Limits | Change them at will | Consent to any change | Suspension or removal takes effect [one hour] after receipt of notice and narrowing takes effect [one] business day after receipt. Widening the Limits, adding an agent or Channel, or permitting subagents requires written acceptance by an Authorized Individual of the other party (Section 17, Changes, suspension and revocation) |
| Aggregate limits | One company-wide cap every vendor must respect | It can only see its own orders | Set per counterparty; any company-wide total is the deploying party’s to enforce (Section 7, Enforcement of Limits; Section 8, Notice of Limits) |
| Click-through terms | Ignored | Its standard terms apply | Ignored unless the Limits permit them (Section 12, Terms presented to agents) |
| Planted instructions | A remedy against manipulation | The same, for its own agents | Mutual prohibition; affected party may avoid (Section 16, Embedded instructions) |
Why a seller would agree, and what it may ask for
Acme asks Brightline Supply, a fictional hardware vendor it already buys from under a master agreement, to sign the Addendum for orders from Acme’s procurement agent. Brightline doesn’t use agents itself, so only Acme lists an agent. Brightline completes only Part 1 of Schedule A, naming who may accept wider limits for it and giving its notice address.
What Brightline gets.
- Binding orders. Brightline can treat an order within the Limits as Acme’s authorized order. Once the parties form a deal, Acme can’t walk away just because its agent placed the order (Section 13, Agent Actions within the Limits).
- Narrow exits. Acme’s ways out don’t turn on second thoughts: the agreed error procedure, unwinding obvious errors, and avoiding orders induced by planted instructions (Section 15, Errors; Section 16, Embedded instructions).
- Fewer bad orders. Acme must enforce its per-transaction and aggregate limits and approval requirements in its own systems (Section 7, Enforcement of Limits).
- No keeping what it received while objecting. Acme must give notice by the rejection deadline and return goods unused. Inspection, storage and return are permitted. Brightline can recover the agreed price for services performed and for use of leased property or licensed rights before rejection, plus its other reasonable out-of-pocket costs of performing before rejection, to the extent not covered by that price. Shipment cuts off rejection of custom or perishable goods (Section 14, Agent Actions outside the Limits).
- A say over wider limits. A widening takes effect only when one of Brightline’s Authorized Individuals accepts it in writing (Section 17, Changes, suspension and revocation).
- Protection if it adds agents. The ban on planted instructions protects Brightline’s own agents too (Section 16, Embedded instructions).
What Brightline gives up. The real concession is reliance beyond the Limits. Today, Brightline could argue that an order placed through Acme’s own account bound Acme, whatever Acme’s internal limit, and under the tool view that argument can succeed. Once Brightline has Schedule A, it can’t rely on appearances beyond the Limits (Section 8, Notice of Limits). Brightline also gives up its checkout terms for agent orders (Section 12, Terms presented to agents) and takes on some administration: sending Confirmation Messages, handling rejections and keeping records (Section 11, Formation, changes and confirmation; Section 14, Agent Actions outside the Limits; Section 18, Records).
What Brightline may ask for.
| Brightline asks | Why | How Acme can respond |
|---|---|---|
| A shorter rejection window | In-stock goods ship the same day. Two business days leaves orders in limbo. | One business day for in-stock goods, or rejection only before shipment. Acme pays return shipping for anything it rejects after delivery. |
| Its standard terms on warranty and returns | Those terms are how it prices risk. | List the terms Brightline needs as Permitted terms in Schedule A, so Acme’s agent may accept them. Or put them into the master agreement once, so they apply to every agent order without the agent having to accept them. |
| No manual checking | It can’t have a person review every agent order. | Routine orders need no manual review: the agreed checks run automatically, and an order outside a range is held until an Acme Authorized Individual approves it (Brightline may instead decline to accept it). Brightline need not check every Limit: a seller that doesn’t check simply bears the risk of an order outside the Limits. The one agreed check is the error-detection procedure (Section 15, Errors), and Schedule A gives Brightline only automated price and frequency checks. Acme runs the quantity check, because only Acme knows its agent’s 90-day average. Beyond that, Brightline’s order system can check what appears on the face of each order automatically from the machine-readable Schedule A: amount, its own aggregate, category, term, prohibited terms, and an approval reference where one is required (Section 5, Human approval). Whether the approval actually happened, and any company-wide total, are Acme’s to police (Section 7, Enforcement of Limits). |
| Payment for over-limit orders filled in good faith | It shouldn’t lose money because Acme’s controls failed. | A restocking fee on over-limit goods it takes back. The draft already covers its reasonable out-of-pocket costs of performing (Section 14, Agent Actions outside the Limits). |
| Its liability cap to apply to refunds | The master agreement caps its liability and may limit remedies. A refund obligation outside the cap is new exposure. | Keep the carve-out only for refunds of amounts Acme actually paid for orders it rejects or avoids, which return Acme’s own money rather than compensate a loss, and let the cap apply to everything else, such as unwinding costs. Or drop the bracketed carve-out if the master agreement’s liability cap and exclusive remedy clauses don’t limit rejection or refunds, for example because the cap already excludes refunds of amounts paid. |
| Shorter record keeping | Six years is costly for a small seller. | Records only of Agent Actions Brightline received, for a shorter agreed period. |
When a seller probably won’t agree. Large marketplaces and software vendors that sell to everyone on one set of terms are unlikely to sign a buyer’s addendum. It is most realistic with vendors a company already has a master agreement with, where agent orders will be frequent enough to matter. With other sellers, sending Schedule A can still help: under the agent view, a seller that knew the agent’s limits has a weaker claim that it reasonably believed the agent could go further.
What the Addendum adds to the law
- Already supported. Notice of a limit generally defeats a claim of apparent authority beyond it (Restatement (Third) of Agency §§ 2.03, 3.03). Parties may set most of their own rules for electronic transactions (UETA § 5). Knowingly keeping the benefit of an unauthorized act can ratify it (Restatement (Third) of Agency §§ 4.01, 4.06). Parties may agree on a security procedure for detecting changes or errors in transmission, and the party that followed it may avoid such an error the other would have caught (UETA § 10(1)); the Addendum extends that approach by contract to errors in the Agent Action itself. A mistake the other party had reason to know of can make a contract voidable (Restatement (Second) of Contracts § 153(b)).
- Needs a contract today. We haven’t found a statute or decision, as of November 2026, that treats a published statement of an agent’s limits as binding notice on a counterparty. The Addendum does that by agreement: within the Limits, Agent Actions bind, subject to the error and planted-instruction rules (Section 13, Agent Actions within the Limits; Section 15, Errors; Section 16, Embedded instructions); beyond them, the other side has notice and can’t rely on appearances (Section 8, Notice of Limits). Beyond the agreed error checks, it doesn’t require the other side to check every action, but a party that doesn’t check bears the risk of an action outside the Limits. It also sets fixed notice periods for changes (Section 17, Changes, suspension and revocation).
- Would need law or industry rules. Binding counterparties who never agreed would take legislation, regulation or network rules. Payment networks’ agent recognition protocols point in that direction.
Source status. The terms and notes were assembled on Oct 11, 2026 from the former Agent-to-Agent Addendum and Agent Mandate and revised on Oct 13 and Oct 14, 2026 (Oct 14: approval amounts for Authorized Individuals in Schedule A, with no maximum for the Chief Financial Officer, with related changes to Sections 5 (Human approval) and 14 (Agent Actions outside the Limits) and the Section 13 (Agent Actions within the Limits) note), and on Nov 11, 2026 (definitions of “Agreement” and “Transaction,” use of leased property and licensed rights in Section 14 (Agent Actions outside the Limits), the confirmation exception in Section 1 (Purpose and precedence), the defined terms “Confirmation Message” and “Operative Message” in Section 2 (Definitions), the rule in Section 14 (Agent Actions outside the Limits) restated in the affirmative, with a rejection period that runs from receipt of the Confirmation Message (or from when a party’s own required Confirmation Message was due), use of goods only with knowledge of where they came from, and payment for performance before a rejection, the confirmation requirements in Section 11 (Formation, changes and confirmation) restated with a minimum content list and extended to one-sided changes and cancellations, and subsections in Sections 2 (Definitions), 5 (Human approval), 11 (Formation, changes and confirmation), 14 (Agent Actions outside the Limits), 15 (Errors) and 17 (Changes, suspension and revocation), section headings added to cross-references, the exclusion of standard terms in Section 12 (Terms presented to agents) extended to all messages forming, changing or cancelling an Agent Transaction, the terms rearranged into six groups in the order a deal proceeds, “received” used throughout for notices and confirmations, with a new Section 19 (Notices) on where notices go and when they are received, and formation and confirmation moved ahead of the sections on Agent Actions within and outside the Limits, without change of substance), and on Nov 13 and 14, 2026 (in Section 15 (Errors), checks may be automated without a separate duty of individual review, an Agent Action outside a range is held until an Authorized Individual of the party whose Designated Agent took it approves it, with notice of the hold when the other party runs the check, the paragraph on missing information was removed, avoidance is limited to a party that followed the procedure, with a deadline running from receipt of the Confirmation Message, and obvious errors are defined, with a notice deadline; in Section 17 (Changes, suspension and revocation), change periods run from the other party’s receipt of notice, and an unaccepted offer lapses on any change to its Designated Agent’s entry in Part 2 of Schedule A; Section 21 (Rights that cannot be varied) retitled; and the Provider Rider removed), and on Nov 15, 2026 (the Chief Financial Officer added to “Approved by” in Schedule A, matching the additional approval recorded in the Agent Mandate). On Nov 18, 2026, the error-notice period was clarified for late or missing confirmations, the records clause was revised to address personal data and legal holds, and paper-form adoption instructions were added to the downloads. On Nov 19, 2026, section 3 and the adoption instructions were revised for consent to later transactions and state standard-form rules (including California’s UETA), the section 9 note was revised to clarify UETA § 9 attribution and credential compromise, section 14(c)(ii) was clarified to avoid double recovery of out-of-pocket costs covered by clause (i), and the section 15 note distinguished UETA’s two error remedies. The Schedule A example also specifies how the agent can settle its own orders in the Channel and JSON (using “unlimited” for the Chief Financial Officer’s maximum). Schedule A and sections 5 and 15 also clarify that transaction approval and release of an error hold leave the agent’s other Limits in force. The statutory references were checked against the statutes on Oct 13, 2026, and cross-references and bracketed periods were proofread. The Restatement references in the law section were checked against the published text on Nov 15, 2026 (Restatement (Second) of Contracts § 153(b)) and Nov 17, 2026 (Restatement (Third) of Agency §§ 2.03, 3.03, 4.01; § 4.06 checked via Henderson v. United Student Aid Funds, Inc., 918 F.3d 1068 (9th Cir. 2019)).
Related: Contracts Formed by AI Agents · Agent Use Clauses · When an Agent Makes a Mistake · Technical Permission vs. Legal Authority