Summary
- Yes, AI agents can form binding contracts. UETA and E-SIGN say a contract isn’t invalid just because software on one or both sides made it without human review.
- UETA applies when both parties agree to transact electronically, which their conduct can show. E-SIGN generally leaves each party free to choose whether to use or accept electronic records or signatures.
- The hard questions are about terms: whether click-through terms an agent accepted are binding, and what happens when two agents exchange conflicting forms.
- What an agent says while negotiating can create liability even if no contract results.
Can software make a contract?
Yes. UETA covers two situations.1
- Agent to agent. A contract can form by the interaction of the parties’ electronic agents, even if no person was aware of or reviewed the agents’ actions or the resulting terms.
- Agent to person. A contract can form between an electronic agent and an individual, including when the individual takes actions they are free to refuse and knows or has reason to know will lead the agent to complete the transaction. Clicking “Buy” on a website is the classic case.
E-SIGN gives the same result for transactions in or affecting interstate or foreign commerce, as long as the agent’s action is legally attributable to the person to be bound.2 For sales of goods, the UCC already allows a contract to be made in any manner sufficient to show agreement.3
One threshold condition: UETA applies only to transactions where the parties have agreed to conduct them electronically, and whether they have is judged from the context and their conduct.4 A company that sets up an ordering API and a vendor that accepts orders through it will usually meet this test. When parties use a paper (non-electronic) standard form, state law such as California’s UETA may require separate consent to transact electronically through a separate, optional agreement, and prohibit conditioning the contract on that consent. Keep evidence of how the parties agreed to use the channel.
State versions differ. Every state except New York has adopted UETA, Illinois most recently in 2021, but several states changed the uniform text when they enacted it, so check the version in the state whose law governs.5 New York relies instead on its Electronic Signatures and Records Act, which has no counterpart to UETA’s rules on electronic agents. There, the electronic agent rule comes from E-SIGN, for transactions in or affecting interstate or foreign commerce.6
Three questions, kept apart
“Is there a contract?” is only the first of three questions. Most confusion comes from treating an answer to one as an answer to all three.
| Question | What it asks | Where the answer comes from |
|---|---|---|
| Formation | Can a contract form when software makes the offer or the acceptance? | UETA and E-SIGN: the use of software is no obstacle, even if no person reviewed it, but the contract must still be valid on other grounds |
| Attribution | Is the agent’s act the company’s act? | E-SIGN § 7001(h) assumes the action is legally attributable. Applicable law and the parties’ agreement determine attribution. Under UETA § 9, a party may prove whose act it was by any means, and its legal effect depends on the context, the agreement and other law. |
| Authority | Was the act within what the company approved, or what it led the other side to believe? | Agency law, corporate delegation and the technical permissions. See Technical Permission vs. Legal Authority |
The statutes answer the first question, by removing the objection that software formed the contract. Disputes are about the second and third, and contracts settle them more often than statutes do.
Where the intent comes from
Contracts require assent. Software can’t intend anything, so where does the intent come from? The statutes’ answer is that contracts can be formed through automated systems without human review of each transaction. Whether a particular act is attributable to the company, and what legal effect it has, still depends on the facts, the parties’ agreement and applicable law.7 In our view, a court is likely to treat a company that deployed an agent to transact as having intended at least the kinds of transactions it set the agent up to make; whether that intent extends to decisions the company did not anticipate is unsettled.
That answer works well for systems that follow fixed rules. It gets harder when an agent makes choices its deployer didn’t anticipate. The argument will be that the company intended some deals, but not this one. Under the tool view, that argument usually fails: the company chose to use a system that makes choices. Under the agent view, it becomes a question of what the company’s instructions and conduct conveyed to the agent.
Which terms apply
Click-through terms
Courts enforce online terms when the user had reasonable notice of them and clearly agreed, for example by clicking a button next to a visible link.8 Terms buried where no reasonable user would look are not enforced.9 These tests were built around what a human would see. When an agent is the one clicking, two questions follow:
- Is notice judged by what a reasonable person would have seen, or by what the agent processed?
- Does notice to the agent count as notice to the company that deployed it?
We haven’t found a reported decision that squarely answers either for AI agents, as of November 2026. Two states give a statutory answer for one kind of deal. For computer information transactions, such as software licenses, governed by Maryland’s or Virginia’s Uniform Computer Information Transactions Act (UCITA), an electronic agent has an opportunity to review terms only if they are made available in a way that would let a reasonably configured electronic agent react to them, and a person who selects and uses an electronic agent to authenticate a record, perform an obligation or make an agreement (including giving assent) is bound by its operations even without human review. The statute separately says which operations count as an agent’s assent, such as operations that in the circumstances indicate acceptance, so a prominently placed link alone settles neither question.10 Several other states have laws that resist contract terms choosing UCITA,11 and the statutes don’t settle how the standard applies to a particular AI system. In Register.com v. Verio, Verio kept querying the database after it knew the terms returned with every response. The Second Circuit affirmed a preliminary injunction because Register.com was likely to prove that Verio accepted the terms by continuing to use the database, even without clicking to agree.12 For an agent’s first visit, preserve the terms as delivered, when they appeared and what the agent did next. Those records help show both notice and assent. The risk that a later click changes a negotiated deal is the reason for the “no override” clause in Agent Use Clauses.
Conflicting forms
When two companies’ agents exchange orders and confirmations with different terms, the result is the same “battle of the forms” that paper purchase orders have always produced. For sales of goods governed by a state’s UCC Article 2, § 2-207 decides which terms control.13 An international sale can be different. Between parties whose places of business are in different countries that have joined the UN Convention on Contracts for the International Sale of Goods (CISG), the Convention can apply by default, even where the contract chooses a U.S. state’s law, and under it a reply that materially changes the offer is generally a counteroffer.14 Louisiana also has its own Civil Code rule for conflicting terms in sales of movables.15 Agents make it faster and more frequent, not different in kind. A master agreement that sets the terms in advance avoids the fight.
Repeated orders and terms by reference
When an agent places the same kind of order again and again, the pattern becomes evidence. Under the UCC, a course of dealing between the parties can supply or explain the terms of their deals,16 so orders accepted and paid without objection help show what both sides understood. The same pattern bears on authority: each order a company pays makes it harder to say the next one wasn’t authorized.
Agents also meet terms incorporated by reference, such as an order form that says “subject to our terms at [link].” Whether those terms bind turns on reasonable notice, the same test as for click-through terms, and the same “no override” clause is the protection.
Signatures and records
Where a law requires a signature or a writing, an electronic signature or record can satisfy it, subject to applicable consent, accessibility, retention and other requirements.17 An electronic signature is a sound, symbol or process attached to or logically associated with a record and executed or adopted by a person with intent to sign.18 When an agent applies a signature, the question is again attribution: whether the signature was the company’s act, which can be shown in any manner, including by the security procedure used.19 Model UETA and E-SIGN both exclude transactions governed by laws on making wills and most of the Uniform Commercial Code—leaving out Articles 3, 4, 4A (funds transfers), 5, 7, 8, 9 and, where enacted, 12, while keeping sales (Article 2), leases (Article 2A) and pre-revision §§ 1-107 and 1-206 (renumbered to § 1-306 and repealed, respectively, under Revised Article 1) within their scope. E-SIGN separately excludes specified notices, such as notices of cancellation or termination of utility service, from § 7001’s electronic-record rule.20 Check the exclusions before letting an agent sign anything formal.
When agents negotiate
An agent that negotiates can make statements about price, features, delivery or policy. Those statements can create liability on their own. In Moffatt, an airline was liable for negligent misrepresentation because its chatbot gave a customer wrong refund information.21 A negotiating agent can also make concessions or promises that become terms of the deal.
Two practical rules follow. Limit what the agent can offer and promise, not only what it can accept. And keep a record of what the agent said, since in a dispute over terms the conversation may be the only evidence.
Worked example
Beta Corp’s procurement agent handles software renewals. It’s instructed to renew a data analytics subscription if the price increase is under 5%. The vendor’s sales agent offers a 4% increase and, in the same message, a new clause: automatic three-year renewal with a 90-day cancellation notice. Beta’s agent accepts.
- Did a contract form? Very likely. Both sides deal electronically, and agent-to-agent formation is expressly allowed.
- Is Beta bound by the auto-renewal term? Probably, under the tool view. The term was presented in the same exchange the agent accepted. Beta’s instructions covered price, not renewal terms, but the vendor had no way to know that.
- What would have helped? An instruction, enforced by the system, to escalate any change to term length or renewal. And a master agreement saying click-through or chat terms don’t modify it.
Checklist
- Confirm the counterparty has agreed to deal electronically, ideally in writing.
- Set terms in master agreements with key counterparties, and state that interface terms don’t modify them.
- Give agents a list of terms that need human approval, and have the system stop any deal with one of those terms until a person approves it.
- Limit what agents may offer or promise, as well as accept.
- Keep full records of every negotiation and acceptance.
- Check the UETA and E-SIGN exclusions before an agent signs formal documents.
Common situations
Three kinds of deal agents already make, and what decides whether the company is held to them.
The agent bought something. Is the company bound?
Short answer: Often, yes, if the order is attributable to the buyer and the parties formed a contract under their agreed ordering process. The account record helps identify whose order it was. Check any approval conditions and whether the seller knew of a limit or should have recognized an obvious error.
UETA lets contracts form between electronic agents with no human review,22 and the UCC accepts any conduct showing agreement,23 so an automated acceptance can form a contract when the parties’ agreed conditions are met. Using the company’s own account or card is evidence that the order was the company’s act,24 and a court has refused to let a business escape a commitment because a computer processed it: in Bockhorst, an insurer whose employees knew of an accident was held, under Kansas waiver law, to a reinstatement its computer issued.25
Internal spending limits protect the company mainly if a check stopped the order before it was sent, or the seller knew about them (see The agent went over its spending limit). Using the goods after learning the material facts can affirm an unauthorized order. If a sales contract already exists, using the goods can also constitute acceptance of the goods under UCC § 2-606 (opens in a new tab). If an order is wrong, tell the seller promptly in writing that you dispute it and reserve your rights, don’t use the goods, and check what rejection or cancellation rights you have before their deadlines run. If a contract formed, refusing conforming goods only because the order broke an internal limit can itself be a breach. In a dispute, the facts that matter are which account or card was used and its limits, where the spending limit was written, what the seller knew, and the logs and the agent’s instructions.
- If you deploy the agent: Limit what the agent’s accounts and cards can do, not only what its instructions say: payment caps, approved vendor lists, blocked terms, escalation to a person, and a way to switch it off. Address agent-placed orders in master agreements with key vendors, and keep a record of every order and the approval in force at the time.
- If you provide the agent: Customers will ask whether your service enforces spending caps or only instructs the agent to respect them, and who pays if a cap fails. Have a documented answer and a contract position before they ask.
- If you’re the seller: The buyer’s account record helps establish who placed the order. Check the agreed steps for a binding purchase. If the agreement requires a person to approve an order, look for that approval before filling it. Your position weakens if you knew the order was outside the agent’s limits, or if it was an obvious error you should have caught. Consider terms that address agent orders, and flag orders far outside a buyer’s history.
The agent clicked through terms. Are the terms binding?
Short answer: The terms may bind the company if it had adequate notice and its agent took a step that clearly signaled agreement, such as clicking “I agree.” If a master agreement already governs, check whether it allows a click to change the deal.
Courts enforce online terms where a reasonable user would have noticed them and clearly agreed.26 We haven’t found a decision on whether that test is applied to what a person would have seen, or to what the agent processed. For software licenses governed by Maryland’s or Virginia’s UCITA, the statute asks whether a reasonably configured electronic agent could have reacted to the terms. If the agent was barred internally from accepting arbitration, liability caps or auto-renewal, check whether the other side knew of the limit and whether the parties had agreed to require separate approval for those terms. If both sides’ agents exchange conflicting forms, UCC § 2-207 decides which terms control in a sale of goods governed by a state’s Article 2 (with an international supplier, check whether the CISG applies);27 a master agreement avoids the question. The facts that matter are when and how the terms were presented, what action signaled agreement, any existing agreement, and the agent’s instructions on acceptable terms.
- If you deploy the agent: Keep a list of terms that need a person’s approval, have a person approve any deal with a new counterparty, and use master agreements that override click-through terms.
- If you provide the agent: Offer a setting that blocks or escalates acceptance of listed terms, and say in your documentation whether the agent reads terms at all.
- If you present the terms: Make terms conspicuous and require a clear act of acceptance, as courts already expect for human users. Consider stating that acceptance by an automated system on a customer’s behalf binds the customer.
The agent bought cloud services or software. How is it different from buying goods?
Short answer: The authority questions are the same as for goods, but the commitment is ongoing. A subscription an agent starts can renew automatically, commit the company to minimum spend, or bring in click-through terms on data use and liability, so a mistake keeps costing money until someone notices.
Ongoing commitments. Committed spend and reserved capacity plans trade a discount for a minimum commitment, often a year or more. An agent told to cut costs may choose one. Treat any commitment longer than the mandate, or any minimum spend, as needing a person’s approval.
Auto-renewal. Renewal clauses bind unless notice is given in time. Some state laws protect business buyers too. New York makes automatic renewal clauses in contracts for service, maintenance or repair of property unenforceable unless the provider serves a written reminder, personally or by certified mail, 15 to 30 days before the customer’s deadline to cancel. The rule doesn’t apply to renewal periods of one month or less.28 Courts have applied it to software-based services tied to the customer’s property: to coding and billing services run on the customer’s records in Healthcare I.Q., and to software installation and maintenance in Cor-Ibs.29 A subscription that only gives access to the provider’s own software may be analyzed differently, so look at what the services are and whose property they concern. Consumer auto-renewal laws generally don’t reach business buyers. The FTC’s 2024 click-to-cancel rule was vacated in 2025,30 and the FTC opened a new rulemaking in March 2026.31
Tool or agent. Under the tool view, the company’s account record supports attribution. Whether the subscription binds the company also depends on the terms and the approvals the parties agreed to require. Under agency rules, a multi-year or minimum commitment beyond the agent’s mandate may not bind the company if the vendor knew or had reason to know it went beyond the agent’s limits.32
Usage-based charges. An agent that provisions cloud resources can create spending with no order at all. Limits have to be set in the provider’s controls, not in the agent’s instructions, and an alert isn’t a limit: many budgets only send notifications while consumption continues. Use a hard spending cap where the provider offers one for the service. Otherwise, rely on service quotas, limits on what the agent may provision, and a tested procedure for stopping resources when a threshold is reached.
Terms and data. Click-through terms often cover data use, liability limits and governing law. An agent that accepts them may give away rights the company would have negotiated. For a software license governed by Maryland’s or Virginia’s UCITA, ask what the company selected the agent to do, whether a reasonably configured agent could react to the terms as presented, and whether this agent’s operations indicated assent. Selecting an agent to compare prices alone does not establish that the company selected it to accept a license. Check the governing-law clause the agent accepted.
- If you deploy the agent: Block new subscriptions and plan changes without approval, set hard spending caps or service quotas at the provider where available (a budget alert alone doesn’t stop spending), have a person own the renewal calendar, and route new vendors through a master agreement. Record these limits in the agent’s Agent Mandate.
- If you provide the agent: Customers will ask whether your agent can start subscriptions, accept multi-year terms or change plans. Make each one a separate setting that can be blocked or escalated.
- If you’re the vendor: Terms accepted through the customer’s account generally bind the customer. Still, make renewal and commitment terms conspicuous and confirm large commitments with a person: a customer disputing an agent-made commitment will point to buried terms and missing notice.
Both sides of the deal
If you deploy agents
- Put master agreements in place with key counterparties.
- Give agents a list of terms that need human approval, and have the system stop any deal with one of those terms until a person approves it.
If you build agents
- Offer customers a setting to block or escalate listed terms, such as auto-renewal or arbitration.
- Say in your documentation whether the agent reads the terms it accepts.
- Keep records of every negotiation your agent conducts. Customers will need them in disputes.
Not the first time
Courts and legislatures have met earlier versions of this problem. Each older answer is a starting point, and the useful question is what has changed enough that it may no longer fit.
| Earlier technology | The question it raised | What may be different with AI agents |
|---|---|---|
| Telegraph and mail | When does an acceptance take effect between parties at a distance? | Formation can happen in milliseconds between two systems. |
| Electronic data interchange (EDI) | Do machine-to-machine messages form contracts? | With EDI, trading partners agreed on the terms in advance. An agent may choose its own terms and counterparties as it goes. |
| Automated phone and web ordering | Is a business bound by the system it built and deployed? | Those systems followed a fixed script. An agent’s behavior isn’t scripted. |
| Payment cards | Who bears the loss when a credential is used without authority? | Card network rules are only beginning to address agent-initiated payments. |
| Electronic signatures | When is an electronic act attributable to a person? | No person adopted the agent’s act at the moment it happened. |
| Algorithmic trading | Who answers for fast automated decisions? | Trading systems act within one market. Agents act across many. |
These comparisons are leads for research, not conclusions.
Open questions
- Outside the Maryland and Virginia UCITA rules for software licenses, is reasonable notice of terms judged by a human standard or by what the agent processed?
- Can a company argue it lacked intent for a deal its agent made in a way no one anticipated?
- When both sides use agents and each claims its terms control, will courts apply UCC § 2-207 unchanged?
- Unif. Elec. Transactions Act § 14(1)–(2) (opens in a new tab) (Unif. L. Comm’n 1999). ↩
- 15 U.S.C. § 7001(b)(2), (h) (opens in a new tab). ↩
- U.C.C. § 2-204(1) (opens in a new tab). ↩
- Unif. Elec. Transactions Act § 5(b) (opens in a new tab); see, e.g., Cal. Civ. Code § 1633.5(b) (opens in a new tab) (non-electronic standard form contracts). ↩
- Unif. L. Comm’n, Electronic Transactions Act (opens in a new tab) (enactment map) (last visited Nov. 7, 2026) (enacted in every state except New York); Ill. Pub. Act 102-38 (opens in a new tab) (2021) (codified at 815 Ill. Comp. Stat. 333). ↩
- N.Y. State Tech. Law §§ 301–309 (opens in a new tab); 15 U.S.C. § 7001(b)(2), (h) (opens in a new tab). ↩
- See Unif. Elec. Transactions Act §§ 9(a)–(b), 14 cmt. 1 (opens in a new tab); Restatement (Third) of Agency § 1.04 cmt. e (opens in a new tab) (Am. L. Inst. 2006). ↩
- Meyer v. Uber Techs., Inc. (opens in a new tab), 868 F.3d 66 (2d Cir. 2017). ↩
- Specht v. Netscape Commc’ns Corp. (opens in a new tab), 306 F.3d 17 (2d Cir. 2002). ↩
- Md. Code Ann., Com. Law § 22-112(b), (e) (opens in a new tab); § 22-107(d) (opens in a new tab); Va. Code Ann. § 59.1-501.13:1(b) (opens in a new tab); § 59.1-501.7(d) (opens in a new tab); see also § 59.1-501.12 (opens in a new tab) (manifesting assent). ↩
- E.g., Iowa Code § 554D.125 (opens in a new tab); Vt. Stat. Ann. tit. 9, § 2463a (opens in a new tab). ↩
- Register.com, Inc. v. Verio, Inc. (opens in a new tab), 356 F.3d 393, 401–04 (2d Cir. 2004). ↩
- U.C.C. § 2-207 (opens in a new tab). ↩
- U.N. Convention on Contracts for the International Sale of Goods arts. 1, 6, 19 (opens in a new tab); Asante Techs., Inc. v. PMC-Sierra, Inc. (opens in a new tab), 164 F. Supp. 2d 1142 (N.D. Cal. 2001) (choice of California law didn’t exclude the Convention). ↩
- La. Civ. Code art. 2601 (opens in a new tab). ↩
- U.C.C. § 1-303(b), (d) (opens in a new tab). ↩
- Unif. Elec. Transactions Act § 7(c)–(d) (opens in a new tab); see also 15 U.S.C. § 7001(a) (opens in a new tab). ↩
- Unif. Elec. Transactions Act § 2(8) (opens in a new tab); 15 U.S.C. § 7006(5) (opens in a new tab). ↩
- Unif. Elec. Transactions Act § 9(a) & cmt. 1 (opens in a new tab). ↩
- Unif. Elec. Transactions Act § 3(b)(1)–(2) (opens in a new tab); 15 U.S.C. § 7003(a)(1), (a)(3), (b)(2)(A) (opens in a new tab). ↩
- Moffatt v. Air Canada (opens in a new tab), 2024 BCCRT 149 (B.C. Civ. Res. Trib.). ↩
- Unif. Elec. Transactions Act § 14 (opens in a new tab). ↩
- U.C.C. § 2-204(1) (opens in a new tab). ↩
- Unif. Elec. Transactions Act § 9(a) (opens in a new tab). ↩
- State Farm Mut. Auto. Ins. Co. v. Bockhorst (opens in a new tab), 453 F.2d 533 (10th Cir. 1972). ↩
- Meyer v. Uber Techs., Inc. (opens in a new tab), 868 F.3d 66 (2d Cir. 2017). ↩
- U.C.C. § 2-207 (opens in a new tab); see also supra note 14 (CISG). ↩
- N.Y. Gen. Oblig. Law § 5-903 (opens in a new tab). ↩
- Healthcare I.Q., LLC v. Tsai Chung Chao (opens in a new tab), 118 A.D.3d 98, 104–05 (1st Dep’t 2014); Cor-Ibs, Inc. v. Bank Leumi USA (opens in a new tab), 2021 NY Slip Op 31516(U) (Sup. Ct. N.Y. Cnty. 2021) (motion to dismiss); see also Cor-Ibs, Inc. v. Valley Nat’l Bank (opens in a new tab), 2024 NY Slip Op 32493(U) (Sup. Ct. N.Y. Cnty. 2024) (agreements never renewed for lack of the statutory notice). ↩
- Custom Commc’ns, Inc. v. FTC (opens in a new tab), 142 F.4th 1060 (8th Cir. 2025). ↩
- Rule Concerning the Use of Prenotification Negative Option Plans, 91 Fed. Reg. 12,318 (opens in a new tab) (Mar. 13, 2026) (advance notice of proposed rulemaking). ↩
- Restatement (Third) of Agency §§ 1.04 cmt. e, 2.03 (opens in a new tab). Unif. Elec. Transactions Act § 9(a)–(b) (opens in a new tab). ↩