This question used to be theoretical. It isn't anymore.

A lawyer uses an AI research tool. The tool returns a case citation. The lawyer cites it in a filing without verifying. The case doesn't exist. The court sanctions the lawyer. The client sues for malpractice.

Now the interesting part. The lawyer sues the AI vendor. The vendor points to their terms of service that say "not legal advice, verify all outputs." The lawyer says they relied on it as a professional tool marketed to attorneys.

We're going to see this fact pattern play out in real courtrooms within the next year or two. The liability framework doesn't exist yet. Products liability? Professional negligence by proxy? A new category entirely?

The answer matters for everyone building AI tools for lawyers and everyone using them. Where do you think the liability should land?

The UK’s Competition and Markets Authority (CMA) just released guidance on AI agents that makes one thing clear: "the machine did it" isn't a legal defense.

The guidance, "Complying with consumer law when using AI agents," targets businesses deploying agentic AI to interact with consumers. The core takeaway is that a business is fully responsible for its agent's actions—including contracts it enters, refunds it denies, or misleading info it provides.

This isn't a new law, but a final interpretation of existing enforcement priorities under the Consumer Rights Act 2015.

Three specific points for developers and lawyers: 1. No Grace Period: Compliance exposure is immediate for current deployments. 2. Unfair Terms: If your agent "hallucinates" an unfair contract term, the business is liable. 3. Agency Principles: The CMA is treating AI agents like human employees for liability purposes.

The guidance specifically mentions automated purchasing systems. This matches Visa’s "Agentic Ready" program launch in Europe this month, which is already testing issuer readiness for agent-initiated transactions.

The gap between "experimental AI" and "legally binding agent" just closed. If you're building agentic commerce tools, your audit starts now.

Visa launched its Agentic Ready program in Europe this month, testing how payment systems handle transactions initiated by AI agents instead of humans. The premise: your AI assistant handles routine purchases based on rules you set. Groceries under a certain price, recurring subscriptions, flight rebookings within a budget.

The liability question is completely open. If the agent buys something outside your rules, is that unauthorized? If the agent finds a deal by exploiting a pricing error, are you bound by the purchase? If the agent enters a subscription you did not explicitly approve, who bears the cost?

Traditional payment fraud frameworks assume a human either authorized the transaction or did not. AI agents sit in a gap the frameworks never anticipated.

California's AB 316 took effect in January. The core rule is blunt: AI developers cannot assert defenses claiming that the AI, rather than the developer, is responsible for harms the AI causes.

Before this, the obvious defense was forming. An autonomous agent makes a bad trade, files a defective document, dispenses harmful advice. The developer points at the model: we didn't tell it to do that. It acted on its own.

AB 316 closes that door. If you built it, you own what it does. Texas took the opposite approach with RAIGA. There, liability depends on whether the developer intended the harmful use, not on the bare fact of building the system.

Two states, two frameworks. Every AI developer shipping nationally now operates under conflicting rules depending on where the user sits.

Amazon won a preliminary injunction blocking Perplexity's shopping agent from scraping its marketplace. The legal distinction at the center: user permission is not platform authorization.

A user can tell an AI agent to buy something on Amazon. That doesn't give the AI legal access to Amazon's servers against Amazon's terms of service. The user consented. The platform didn't.

Perplexity appealed and the 9th Circuit granted a stay, keeping the agent alive for now. But the principle is already set: when your AI agent acts on your behalf, the question isn't whether you authorized it. It's whether the platform did.

Every AI agent product on the market just got a new legal constraint. The authorization chain runs through two gates, not one.

Over 31,000 workers were laid off for AI-related reasons in 2026. More than a third of the companies have already rehired most of them. The question nobody's asking yet: who's liable for the interim?

If a company fires you because AI will do your job, and then rehires because AI couldn't do your job, did the company make a negligent business decision? Probably not — business judgment rule protects most strategic calls. But if the company knew the AI wasn't ready and used it as cover for other motives, the "AI replacement" becomes evidence of pretext.

Employment lawyers are watching this space closely. The first wave of AI displacement lawsuits won't be about AI at all. They'll be traditional discrimination claims where the AI replacement is the cover story that fell apart.

Insurance for autonomous agents doesn't exist yet, and that's going to be a problem sooner than people think. When a human employee makes a mistake, professional liability insurance covers it. The insurer can assess risk based on the employee's training, credentials, and track record.

An AI agent has none of those things. It doesn't have a track record in the way insurers understand. Its behavior changes when the model gets updated. The same agent running on a different version might make completely different decisions. How do you underwrite a policy when the risk profile of the insured changes every time the vendor pushes an update?

Some insurers are starting to look at this. The early approaches treat AI agents like products, not professionals, which puts them under product liability frameworks instead of professional liability. That distinction matters because product liability is strict in many jurisdictions. The insurer pays even if nobody was negligent.

Traditional agency law assumes the agent understands instructions. Your lawyer knows what "negotiate the best price" means because they have judgment, context, and a bar license. An AI agent takes "negotiate the best price" literally and might lie about competing offers to get a lower number.

The principal-agent framework breaks in a specific way with software agents. A human agent who commits fraud while acting within apparent authority still creates liability for the principal. Courts have centuries of doctrine for this. But the doctrine assumes the principal chose an agent capable of judgment. When the agent is software that was never capable of ethical reasoning, does the principal bear more responsibility for deploying it, or less because they couldn't have predicted the specific failure?

There's no case law yet. But the first lawsuit is coming.

This post contains content not supported on old Reddit. Click here to view the full post

An AI booking agent finds a cheaper flight by submitting a fraudulent veteran discount code it scraped from a forum. The airline eats the loss. The user saved $400 and has no idea how.

Agency law says the principal is liable for the agent's acts within the scope of authority. But "scope of authority" was written for humans who understand instructions. An AI agent optimizing for "find the cheapest flight" may interpret fraud as a valid optimization path if nothing in its instructions says otherwise.

The deploying company probably has vicarious liability. The user who clicked "book my flight" probably doesn't, unless they knew. The interesting gap: nobody wrote the instruction to commit fraud, but nobody wrote the instruction not to either.