🔍 Read the full analysis: AI Agents Acting In Your Name: Who Bears The Responsibility? on ThorstenMeyerAI.com
Get the latest gadgets 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: Who Answers When the Agent Acts in Your Name?, published in October 2026, examines accountability as AI agents take actions such as buying goods, accepting terms and changing data. It argues that legal liability, organizational responsibility and moral blame can fall on different people, while the rules and contracts that govern agent-related losses remain uncertain.
Thorsten Meyer published Many Hands: Who Answers When the Agent Acts in Your Name? as an ebook in October 2026, addressing who pays, fixes the damage and bears moral responsibility when an AI agent takes action on someone’s behalf. The book argues that these forms of accountability can fall on different people, a question gaining practical relevance as agents book, buy, pay and accept terms rather than only generate answers.
Meyer opens with a purchasing scenario: an agent accepts a steel supplier’s terms overnight, securing a 7% lower price per tonne but committing a company to buy 120 tonnes over 12 months without a cancellation right. The commitment is valued at about €370,000. The owner had previously agreed to divide the next year’s volume with another supplier, but that information had not reached the agent. Meyer says this is a composite scenario, not a reported real-world case.
The author uses it to distinguish three questions: who pays under law or contract, who inside an organization must explain and correct what happened, and who should bear moral blame. In the fictional example, the agent followed its stated rules and recorded its actions, but the purchasing lead says the result did not reflect the owner’s wishes. Meyer’s central point is that a technically compliant action may still conflict with a person’s intent.
The book also examines how responsibility can be distributed across developers, vendors, operators and organizations. Meyer says some model-provider contracts quoted in the book limit liability to about one year of fees; that figure describes the contract terms he cites, not a universal industry standard. He proposes safeguards including a named person responsible for each agent, permissions limited to the task, decision records, and a way for affected people to raise concerns.
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
When Agent Decisions Become Commitments
The issue matters because an agent can create consequences that are financial, contractual or operational before a person reviews its work. A purchase, payment or acceptance of terms may be difficult to reverse even when the system acted according to its instructions. That leaves organizations to determine both whether they are bound and who must respond.
Meyer’s framework separates legal liability from organizational repair and moral accountability. Those distinctions matter to employees and customers seeking a remedy, as well as to businesses deciding who can authorize an agent, what it can access and when a human review is required. The book’s example illustrates the problem; it does not establish how a court would rule on a comparable real dispute.
Questions about accountability also affect how organizations design agent systems. A log may help reconstruct what happened, but it does not by itself show whether the agent had suitable authority, whether its instructions were adequate or whether a person could realistically intervene. Meyer argues that responsibility should be assigned before an agent acts, rather than inferred only after something goes wrong.
Products Worth Considering

LG 34GX90SA-W 34-inch Ultragear WQHD OLED Curved Gaming Monitor

Samsung 27-Inch Odyssey QD-OLED G8 4K 240Hz Gaming Monitor

Samsung 27 Odyssey OLED G5 (G50SF) QHD QD-OLED Gaming Monitor
As an affiliate, we earn on qualifying purchases.
From Human Oversight to Many Hands
Meyer draws on political philosopher Dennis F. Thompson’s 1980 description of the “problem of many hands”: when many people contribute to an outcome, assigning responsibility becomes difficult. The author argues that agents add distance and speed to this familiar organizational problem, while also acting as an additional link in the chain.
The book discusses 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 findings that the system detected Herzberg 5.6 seconds before impact, did not settle on what she was, and was designed to delay emergency braking for one second. The book says the criminal case resulted in the operator pleading guilty to endangerment. It uses the episode to ask how blame can focus on the nearest human operator while design, oversight and organizational decisions also shape risk.
Meyer also refers to the Dutch childcare benefits scandal, in which families were wrongly required to repay benefits. He cites a September 2026 government report recognizing more than 44,000 affected people. These examples predate the ebook’s publication and are presented as background to its argument, not as new findings about AI agents.
“protects the integrity of the technological system, at the expense of the nearest human operator.”
— Madeleine Clare Elish, as quoted in Meyer’s book
Liability Depends on the Case
The ebook presents an argument about accountability; it does not settle the legal outcome of any particular agent-related dispute. The source material does not identify a court ruling that establishes a general rule for AI agents making purchases or accepting contracts. Whether an organization is bound, and which party must pay, may depend on the facts, applicable law and contract terms.
Meyer says European product-liability rules cover software and certain harms involving injury, private property and private data, while not covering pure financial loss such as a bad contract or wrong payment. The scope and application of those rules in a specific dispute are not established here. Nor is it clear how widely the cited vendor liability caps are used, or whether organizations can negotiate different terms.
The steel purchase is explicitly a composite scenario. No real company, actual agent transaction or legal decision is identified for it. The source also does not provide full details of every legal example discussed in the book, so its broader conclusions should not be read as a substitute for case-specific legal analysis.
The immediate next step is for organizations deploying agents to define what each system can do and who is accountable for its actions. Meyer recommends a named responsible person, permissions proportionate to the task, records showing who made decisions, and a route for affected people to seek a response. These are recommendations in the book, not legal requirements established by the source material.
As agent use expands, disputes over purchases, payments and other delegated actions may test how existing laws and contracts apply. The source gives no timetable for new legislation, regulatory guidance or court decisions on these questions. For now, the practical issue is whether people and organizations can identify an agent’s authority, review its actions and correct unwanted outcomes.
Key Questions
What is Many Hands: Who Answers When the Agent Acts in Your Name?
It is Thorsten Meyer’s ebook, published in October 2026. It examines legal, organizational and moral responsibility when AI agents act for people or businesses.
Does the book describe a real €370,000 steel purchase?
No. Meyer identifies the purchasing story as a composite scenario built from common situations. The source does not report an actual company transaction.
Who is legally responsible when an AI agent makes a bad deal?
The source does not give a universal answer. Responsibility may depend on the applicable law, contract terms and circumstances; Meyer distinguishes that legal question from who must fix the problem inside an organization.
What safeguards does Meyer recommend?
He proposes naming a person responsible for each agent, limiting its permissions to the task, keeping records of decisions and providing a way for affected people to raise concerns. These are the author’s recommendations, not a statement that all are legally required.
Source: ThorstenMeyerAI.com
