# Who is responsible when an AI agent gets it wrong?

By the STACK team. Published 13 November 2026.

The person or company that runs it. This article covers a 2024 tribunal decision, a United States statute, and what the owner of an agent needs in order to carry that responsibility.

Agents now send email, make calls, pay for things and sign up for services on behalf of a person or a company. When one of those actions is wrong, somebody has to answer for it. In the two sources described here, that is the person or company the agent acted for. Neither source treats the agent as a party.

This article is not legal advice. The two sources are from Canada and the United States, and the law differs between countries.

## Moffatt v. Air Canada

In November 2022 Jake Moffatt needed to fly from Vancouver to Toronto after a death in the family, and asked the chatbot on Air Canada’s website about bereavement fares. The chatbot answered that a passenger who had already travelled could apply for the reduced fare within 90 days of the ticket being issued. A page elsewhere on the same website said that the fare could not be claimed after travel. Mr Moffatt booked two flights for $794.98 and $845.38, in Canadian dollars, and applied for the reduction afterwards. Air Canada refused it.

Before the Civil Resolution Tribunal of British Columbia, Air Canada argued that it could not be held liable for information given by its chatbot. The tribunal member read this as a claim that the chatbot was a separate legal entity responsible for its own actions, and called it “a remarkable submission”. He held that the chatbot was part of Air Canada’s website and that Air Canada was responsible for all the information on that website, whether it came from a static page or from a chatbot.

The tribunal found negligent misrepresentation: Air Canada had not taken reasonable care to ensure that its chatbot was accurate. On 14 February 2024 it ordered Air Canada to pay $812.02, made up of $650.88 in damages, $36.14 in interest and $125 in tribunal fees.

Two details of the decision concern evidence. Air Canada gave the tribunal no information about how its chatbot worked. It also did not produce the contract terms it relied on or the fare it said would have applied, and the tribunal drew an inference against it for the missing fare. An Air Canada representative had acknowledged the chatbot’s wording in February 2023, about three months after the conversation, and said the issue had been noted so that the chatbot could be updated.

The decision has limits as a guide. It is a small claims decision from one Canadian province. It concerned information given to a customer, and did not concern an agent that acts, for example by paying or by accepting an offer.

## Contracts made by software, in United States law

United States federal law has addressed software that acts without a person present since 2000. The Electronic Signatures in Global and National Commerce Act defines an electronic agent as a computer program or other automated means used independently to initiate an action or respond to one, without review by an individual at the time.

The Act provides that a contract may not be denied legal effect solely because electronic agents were involved in forming it, so long as the action of the electronic agent is legally attributable to the person to be bound. The contract is therefore valid, and the party to it is a person. The Act does not say when an action is attributable to a person, which is left to other law.

## What this requires of the owner

Both sources place responsibility on the person or company behind the software. In practice that party has to be able to say what its software did. Air Canada did not show the tribunal how its chatbot worked or what fare would have applied, and the missing evidence counted against it.

An owner who expects to answer for an agent therefore needs four things. The first is a record of what the agent did and said, complete enough to be given to someone else. The second is a statement of what the agent was permitted to do, set before it acted. The third is the ability to decide certain actions personally before they happen. The fourth is a way to stop the agent at once.

## How a STACK account provides them

Every action of every agent in an account is written to the record, whether it ran or was refused, and kept for 365 days. Entries are append-only and linked by hash. With controls on, the owner can read the record, export it and verify it, and a third party can check an exported pack without access to the account.

What an agent may do is set in three places. Each agent holds a grant to each service it uses, which names the operations and parameters it may use there. Prepaid credit sets the most it can spend. With controls on, a policy adds rules on spending, recipients and kinds of action, and keeps numbered revisions that show who changed what.

With controls on, a rule can hold an action until the owner or an admin member approves it in a signed-in browser. An approval covers one exact call and works once. An agent cannot approve its own action or change its own controls.

Revoking an agent’s Passport stops it at its next request. The record of what it did before that is kept.

For the other side of a transaction, an account can show that an identified person stands behind an agent. The owner can complete an identity check, and a public lookup then states, in a statement signed by STACK, that the agent is active and that its owner is verified. It shows nothing else about the owner.

None of this changes who is responsible. It is what the owner uses to show what the agent was permitted to do, what it did and when it was stopped.

## Sources

- [Moffatt v. Air Canada, 2024 BCCRT 149](https://decisions.civilresolutionbc.ca/crt/crtd/en/item/525448/index.do)
- [15 U.S.C. 7001: electronic agents, subsection (h)](https://www.law.cornell.edu/uscode/text/15/7001)
- [15 U.S.C. 7006: definitions](https://www.law.cornell.edu/uscode/text/15/7006)
- [STACK: how controls work](/product/controls)
- [STACK: every service and its price](/services)

To correct anything here, write to hello@getstack.run.

## Start with 14 days free.
