# Agent Transaction Addendum

General information, not legal advice. Adapt to your agents, contracts and jurisdiction. From Agent Authority, a legal reference by Obehi Ota.

**Before adopting a paper standard form.**

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.

## Adoption clause

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

Schedule A is shared with the other party.

### Part 1: Contacts

Each party completes this part, even if it uses no agents.

| Field | What to fill in | Example: Brightline | This party |
|---|---|---|---|
| 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.

| Field | What to fill in | Example: Acme procurement agent | This 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 | **Acme, before sending:** quantity of any product in an order more than 2× the agent’s average daily units of that product over the past 90 days or, for a product with less than 90 days of order history, more than 50 units. **Brightline, before accepting:** price more than 10% above Brightline’s list price in effect when the order is received, or more than 5 orders from the agent in an hour. All checks are automated, and neither party needs information from the other to run them. An order outside a range is held and not sent or accepted until an Authorized Individual of Acme, whose agent placed it, approves it. Brightline notifies Acme through the Channel of any order it holds. |  |
| 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 |  |

Approved by: ______  Title: ______  Date: ______

## 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

#### 4. Authority

Each Designated Agent is authorized to act for its party only within its Limits and only through the Channel. Neither party grants its Designated Agents any other authority, express or implied.

#### 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 (illustrative)

An illustrative mapping of the example entry. The error-detection ranges are not authority limits. If this file and the signed Schedule A differ, the signed Schedule A controls.

```json
{
  "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]"
}
```
