🔍 Read the full analysis: Who Answers For The Actions Of An AI Agent In Your Name? on ThorstenMeyerAI.com
Get smart everyday buys delivered free with Prime
- Fast, free delivery on millions of items
- Prime Video, Amazon Music and more included
- Member-only deals all year
TL;DR
Thorsten Meyer’s ebook Many Hands, released in October 2026, examines responsibility when AI agents act on behalf of people and organizations. It separates legal liability, organizational responsibility to explain and repair harm, and the moral question of who should have acted differently. The book argues that the answers can fall on different people, while legal and contractual protections may leave some financial losses difficult to recover.
Author Thorsten Meyer published Many Hands as an ebook in October 2026, examining who is responsible when an AI agent buys goods, accepts terms or otherwise acts in someone’s name. The book separates the question of who pays for a loss from who must explain and fix a mistake, and from who bears moral responsibility—questions that can have different answers.
Meyer introduces the issue through a composite purchasing scenario, not a reported real-world incident. In it, an agent accepts a steel supplier’s terms overnight, securing a lower price but committing a company to buy 120 tonnes over a year without a cancellation right. The commitment is valued at about €370,000. The owner had agreed the day before to divide next year’s volume with another supplier, but that information had not reached the agent.
The example illustrates the distinction the book draws between following an agent’s rules and following an organization’s intentions. Meyer writes that the agent’s actions were consistent with its rules and documented in a log, while the purchasing lead said, “Nothing in it was wrong, and nothing in it was what she wanted.” The scenario is presented as an illustration of common situations, not evidence of an actual contract or dispute.
The book’s central framework asks three questions: who pays, who must explain and repair the outcome, and who should have acted differently. Meyer says those questions involve, respectively, law and contracts, organizational processes, and moral judgment. He also argues that responsibility can be pushed toward the person closest to an action, while designers and other contributors remain less visible.
Many Hands · the core idea
One question, three answers
"Am I liable if the agent does it in my name?" sounds like one question. The book splits it into three, because agent systems pull the answers apart.
Decided by courts, contracts and insurers, on their own timetable.
In Theresa's caseHer company will almost certainly pay for the steel, whatever it later recovers from others.
Decided inside the organization: who must say what happened and what will change.
In Theresa's caseTheresa explains it to the second supplier, her staff and perhaps her bank.
Who owes the people affected an acknowledgment. Often answered last, if at all.
In Theresa's caseStill open when she reaches the motorway.
The hands behind one overnight order
Introduction · a composite scene from the book. None of them saw the acceptance before it went out.
- Model makertrained the language model
- Vendorbuilt the agent on top of it
- Consultantwrote its rules with her staff
- Supplier's portalaccepted the declaration at 2:14 a.m.
- Her companyswitched it on; Theresa signed the rules
“The moral crumple zone protects the integrity of the technological system, at the expense of the nearest human operator.”Madeleine Clare Elish (2019), quoted in Chapter 1
Source: Thorsten Meyer, Many Hands: Who Answers When the Agent Acts in Your Name? (ebook, October 2026; law as of 16 October 2026), Introduction and Chapter 1. Theresa is a composite built from common situations, labeled as such in the book.
Powered by Thorsten Meyer AI
Three Different Tests of Responsibility
The framework matters because an AI agent can carry out an action quickly and within the access it has been given, while still producing an outcome that conflicts with a person’s intent. A company may then face separate questions about financial liability, internal accountability and the steps needed to prevent a repeat. A court’s answer to who owes money may not identify who had the power to correct an unsafe process.
Meyer argues that this gap can leave the nearest human operator or employee carrying the blame, even where decisions about system design, permissions and oversight involved many people. The book uses the term “moral crumple zone,” coined by anthropologist Madeleine Clare Elish, for cases in which a human near an automated system absorbs responsibility for failures involving a wider technical and organizational structure. That is an argument about accountability, not a finding that every agent error has the same cause.
For organizations using agents to make purchases, change records or accept terms, the practical issue is whether the agent’s authority matches the task and whether people can review or stop its actions. Meyer proposes assigning a named person to each agent, limiting its permissions, keeping records of decisions and providing a route for affected people to raise concerns.
Products Worth Considering

HP Sprocket Photo Booth Machine Instant Color Photo Printer with 10.1 Touchscreen, LED Ring Light, 250+ Frames, 3×4 ZINK Paper, QR Code Shar

Dell UltraSharp U2725QE 27-Inch 4K UHD IPS Black Monitor

Logitech MX Keys S Wireless Keyboard, Graphite
As an affiliate, we earn on qualifying purchases.
Cases Behind the Accountability Debate
Meyer connects the book’s argument to earlier debates about automated decision-making and shared responsibility. One example is the 2018 fatal crash in Tempe, Arizona, involving a self-driving test vehicle and pedestrian Elaine Herzberg. Meyer cites the U.S. National Transportation Safety Board’s account that the system detected Herzberg before impact but did not settle on what she was, and that its design delayed emergency braking. The board’s investigation identified several contributing factors, including the operator and company oversight and safety practices.
The criminal case did not resolve every question about organizational responsibility: the safety operator pleaded guilty to endangerment. Meyer discusses the case alongside Elish’s concept of the moral crumple zone to ask how responsibility is assigned when a person monitors an automated system but has limited ability to intervene reliably.
The book also refers to the Dutch childcare benefits scandal, in which tens of thousands of families were wrongly required to repay benefits. Meyer describes responsibility as distributed across institutions and decision-makers rather than attributable to a computer alone. He cites a September 2026 government report as recognizing more than 44,000 affected people. These examples provide background for the book’s argument; they are not direct evidence about the performance of today’s purchasing agents.
““Who pays is the legal question. Who has to explain and fix it is the organizational one. Who should apologize is the moral one.””
— Thorsten Meyer, summarizing the book’s framework
Where Liability Still Has Gaps
The source material presents legal interpretations advanced by the book, not a legal ruling about AI agents in general. Meyer says Europe’s product liability rules cover software and certain harms, including injury, damage to private property and private data, but do not cover pure financial losses such as a bad contract or incorrect payment. The scope and application of laws depend on the facts and jurisdiction; the article cannot establish how a particular agent-related dispute would be decided.
Meyer also says some model-provider contracts cap liability at about one year of fees. The cited source does not provide the contract terms, identify how widely that limit is used, or establish that it applies to every provider. It is also unclear how many real-world disputes involving autonomous agents have tested these contractual and legal questions, or how courts would allocate responsibility among users, employers, developers and vendors.
The steel purchase is explicitly a composite scenario. It does not establish that an agent entered a real €370,000 contract or that a company suffered that loss. The book’s proposed safeguards are recommendations, not proof that a particular design will prevent errors or settle liability.
How Agent Safeguards May Develop
Many Hands: Who Answers When the Agent Acts in Your Name? is available as an ebook, according to Meyer’s October 2026 announcement. The source lists Apple Books, Barnes & Noble, Kobo, Thalia, Bookshop.org, Smashwords, Fable and Vivlio as sellers. Meyer also describes a short video about the book; its narration uses an AI voice clone of the author.
The broader accountability questions will depend on how organizations configure agents and how regulators, courts and contract negotiations address actions taken by software on another party’s behalf. Meyer recommends named responsibility, task-sized permissions, decision records and a way for affected people to respond. Whether those measures become common practice, and how existing legal rules apply to specific agent-driven transactions, remains unsettled.
Key Questions
What is Many Hands about?
Many Hands is Thorsten Meyer’s October 2026 ebook about who answers when an AI agent acts for a person or organization. It distinguishes legal liability, organizational responsibility to explain and fix an outcome, and moral responsibility.
Did an AI agent really make the €370,000 steel purchase?
The source describes the purchase as a composite scenario used to introduce the book. It does not report an actual transaction or confirmed financial loss.
Does an agent’s mistake automatically make its user legally responsible?
The source does not establish a universal rule. Meyer argues that law, contracts and the facts of a dispute determine who pays; responsibility may differ across jurisdictions and cases.
What safeguards does Meyer recommend?
He proposes assigning a named person to each agent, limiting permissions to the task, keeping records of decisions and providing a channel for affected people to raise concerns.
What remains unsettled about AI-agent accountability?
The source does not show how courts will allocate responsibility in future agent-related disputes, how widely vendor liability caps apply, or how existing laws will treat particular financial losses caused by agent actions.
Source: ThorstenMeyerAI.com
