# My AI agent placed an order or accepted terms on my behalf. Am I legally bound by it, and can I undo it if the agent got it wrong?

**Short answer:** Usually yes, if the agent was yours and acting on your instructions. In the US, the federal E-SIGN Act says a contract can't be denied legal effect just because an electronic agent formed it, as long as the agent's action is legally attributable to the person to be bound (15 U.S.C. 7001(h)). The Uniform Electronic Transactions Act (UETA), adopted in most states, goes further: a contract can be formed by the interaction of electronic agents even if no person saw or reviewed the terms (section 14), and an electronic record is attributable to a person if it was that person's act, which can be shown in any manner, including by a security procedure (section 9). UETA's built-in escape hatch is narrow. Section 10 lets an individual avoid a mistaken record made while dealing with someone else's electronic agent that gave no chance to prevent or correct the error, if they promptly say so and return what they received. It isn't written for your own agent's mistakes; those fall to the general law of mistake and the contract's terms. So the practical protection is before the click: limits on what the agent may agree to, and a record of exactly what you authorized. Not legal advice; the rules vary by state and country.

## Checklist
1. Assume an order or sign-up your agent completed with your account, card or credentials binds you, the same as if you had clicked it yourself. Plan your controls around that, not around undoing it later.
2. Write down what the agent is allowed to agree to: which merchants or services, maximum amounts, contract length, auto-renewal, and whether it may accept new terms of service at all.
3. Keep the agent from accepting terms or placing orders outside that list on its own. Route anything new (a new vendor, a subscription, a minimum term, an amount above your threshold) to a person, and bind the approval to the exact merchant, amount and terms.
4. Give the agent its own credential (a scoped key, virtual card or delegated payment token) instead of your main login, so its actions are traceable to that credential and you can cut it off.
5. Keep the merchant's confirmation page, the terms version shown at checkout, the order id and your approval together, recorded at the time and outside the agent.
6. If the agent got it wrong, act fast: tell the other party in writing that the order was a mistake and you don't intend to be bound, don't use what was delivered, and offer to return it. Then check the merchant's own cancellation and refund terms.
7. If the mistake involved a card charge, also look at the card-dispute route (billing error or merchant dispute), which is separate from whether the contract binds you.
8. If you run the merchant side, give buyers' agents and the people behind them a clear chance to review and correct an order before it's final. UETA section 10 lets an individual avoid an error made with your electronic agent when your system gave no such chance.

## Is a contract or order my AI agent made legally binding on me?
- The federal E-SIGN Act, 15 U.S.C. 7001(h), says a contract or record relating to a transaction in interstate or foreign commerce may not be denied legal effect, validity or enforceability solely because its formation, creation or delivery involved the action of one or more electronic agents, so long as the action of any such electronic agent is legally attributable to the person to be bound.
- UETA, a uniform state law most states have adopted, defines an electronic agent as a computer program or other automated means used independently to initiate an action or respond to electronic records, in whole or in part, without review or action by an individual. Virginia's enactment (Va. Code 59.1-480 and following) is a typical example. Section 14 (Va. Code 59.1-492) says a contract may be formed by the interaction of electronic agents of the parties, even if no individual was aware of or reviewed the agents' actions or the resulting terms, and that the terms are determined by the substantive law that applies to the contract.
- Section 9 (Va. Code 59.1-487) says an electronic record or signature is attributable to a person if it was the act of the person, which may be shown in any manner, including the efficacy of a security procedure applied to identify the person. Its effect is decided from the context and circumstances at the time, including the parties' agreement. UETA also applies only between parties that have agreed to transact electronically, which can be inferred from their conduct (section 5).
- Researchers are working on how these older rules map onto today's AI agents. Stanford CodeX's Agentic GenAI Transaction Systems project starts from the hypothesis that UETA, E-SIGN and related frameworks can address many of the issues agentic AI transactions raise, with attribution of actions to legal parties as a core problem.

## Can I cancel or avoid a purchase my AI agent made by mistake?
- UETA section 10 (Va. Code 59.1-488) has two error rules. If both parties agreed to a security procedure to detect errors and only one followed it, that party can avoid the effect of the changed or erroneous record. And in an automated transaction involving an individual, the individual can avoid the effect of an error they made while dealing with another person's electronic agent, if that agent gave no opportunity to prevent or correct the error and the individual promptly notifies the other person, takes reasonable steps to return or destroy what they received, and hasn't used or benefited from it. These two rules can't be varied by agreement.
- Neither rule is written for your own AI agent misreading your instructions. In that case section 10 points to other law, including the law of mistake, and to the contract itself. Outcomes depend on the facts and the state, so the merchant's cancellation policy and a fast, clear notice are often your best practical route.
- A card dispute is a separate question from whether the contract binds you. US card rules treat charges by someone you gave authority to, who then exceeds it, as authorized until you tell the issuer otherwise; see the related answer on disputing an agent's card purchase.

## What records do I need if my AI agent's order or contract is disputed?
- Attribution and error disputes turn on what you actually authorized and what the other side's system showed. Keep, outside the agent and made at the time: the instruction or policy the agent acted under, the limits in force, any approval for this order bound to the exact merchant, amount and terms, the merchant's confirmation page and terms version, and the order id.
- A summary the agent writes afterwards, or a chat log it can edit, is weak evidence of what it was told or shown. An approval recorded before the order, and checked against the order before it was sent, is much stronger.

## Ask Rightshold (free, no key)
Add the MCP server https://www.rightshold.com/mcp to Claude, Cursor, ChatGPT, Grok or VS Code (one-click setup: https://www.rightshold.com/start?ref=seo), then ask: "Before you place this order or accept these terms, ask me to approve the exact merchant, amount, contract length and terms version, and wait for my yes or no."

```json
{
  "tool": "request_human_approval",
  "arguments": {
    "summary": "Sign up for DataCo Pro: $49/month, auto-renews monthly, cancel anytime; terms version 2026-10-01.",
    "action": {
      "type": "purchase",
      "merchant_domain": "dataco.example",
      "amount_minor": 4900,
      "currency": "USD",
      "terms_version": "2026-10-01"
    },
    "expires_in_minutes": 60
  }
}
```
- Needs your API key. You decide once with decide_human_approval, and the decision is a signed, timestamped receipt on Rightshold's ledger.
- Before the agent sends the order, verify_human_approval (free) checks that the order matches what you approved, so a different merchant, amount or terms version can't ride on the same yes.
- For routine purchases, set_spend_policy and authorize_spend give the agent's credential per-purchase and daily caps and an allowed-merchant list, with a signed allow or deny for each purchase.

_Rightshold records approval requests, your signed decisions and spend checks on a hash-chained ledger. It doesn't decide whether a contract binds you, read merchants' terms, cancel orders or move money, and it only helps if your agent's code waits for an approval or an allow before acting. Not legal advice; the rules differ by state and country, so ask a lawyer about a specific dispute._

## Sources
- [15 U.S.C. 7001 (E-SIGN Act), subsection (h): Electronic agents (Cornell LII)](https://www.law.cornell.edu/uscode/text/15/7001)
- [Code of Virginia, Title 59.1, Chapter 42.1: Uniform Electronic Transactions Act (definitions 59.1-480, attribution 59.1-487, change or error 59.1-488, automated transactions 59.1-492)](https://law.lis.virginia.gov/vacodefull/title59.1/chapter42.1/)
- [Stanford CodeX: Agentic GenAI Transaction Systems (UETA, E-SIGN and agentic AI transactions)](https://law.stanford.edu/codex-the-stanford-center-for-legal-informatics/projects/agentic-genai-transaction-systems/)

## Related
- [Can you dispute a purchase your AI agent made with your card?](https://www.rightshold.com/answers/can-you-dispute-a-purchase-your-ai-agent-made-with-your-card)
- [Requiring quote-bound approval before an agent payment settles](https://www.rightshold.com/answers/how-to-require-quote-bound-approval-before-an-agent-payment-settles)
- [Stopping an AI agent from signing up for free trials and subscriptions that auto-renew](https://www.rightshold.com/answers/how-to-stop-an-ai-agent-from-signing-up-for-free-trials-and-subscriptions-that-auto-renew)
- [Requiring human approval before an AI agent spends money](https://www.rightshold.com/answers/how-to-require-human-approval-before-an-ai-agent-spends-money)

_Not legal advice. Updated 2026-11-10. JSON: https://www.rightshold.com/answers/is-your-business-bound-by-a-purchase-or-contract-your-ai-agent-agreed-to.json_