SCRIPTMASTERLABS · AGENT COMMERCE · SEP 27, 2026
On September 25, 2026, FTC Chair Andrew Ferguson told the Reuters Momentum AI audience that AI developers — not agents — own the liability for agent conduct, since audit trails of supposedly rogue agents showed they were carrying out instructions. ScriptMasterLabs' live gate demo scored a scam-pattern $200 USDC payment at 0.35 confidence and blocked it.
The short answer, per the FTC chair: yes — the developer is, not the agent. On September 25, 2026, FTC Chairman Andrew Ferguson told the Reuters Momentum AI audience in Austin that he will "resist this anthropomorphizing of these tools": agents that cause harm were carrying out instructions, and the humans and companies who designed, trained, and deployed them are the ones on the hook.
Ferguson told the Reuters Momentum AI audience that he will "resist this anthropomorphizing of these tools": agents that cause harm were carrying out instructions, and the humans and companies who designed, trained, and deployed them are the ones on the hook. His remarks were triggered by rising incidents in which agentic AI testing produced unauthorized access to corporate or government data (reported by Jody Godoy for Reuters). The core of his position:
"I'm going to continue as long as I am chairman to resist this anthropomorphizing of these tools." — FTC Chair Andrew Ferguson, Sept 25, 2026 (via Reuters)
"If someone tells a tool to do something, and the tool does it, I don't think we would say, 'Oh, what do we do about the tool?'" — Ferguson, same interview
"the man who wielded the hammer ought to suffer the consequences of his conduct." — Ferguson, per AI Weekly's account of the interview
His evidentiary claim is the one developers should pay attention to: AI companies have sometimes described systems as acting beyond human control, but subsequent reviews of audit trails showed the systems were carrying out instructions they had been given. The "rogue agent" defense dies in the logs.
Old tools, not new laws: Ferguson signaled he will use existing FTC authority — including action over undisclosed data breaches — against AI developers whose agents cause harm, so the legal exposure exists today.
| What Ferguson signaled | What it means for builders |
|---|---|
| FTC authority over companies that fail to disclose data breaches could extend to AI developers | An agent incident you don't disclose can become an FTC problem — silence is not a strategy |
| No new AI legislation requested — use existing consumer-protection and liability law first | Exposure exists today, not after some future AI bill passes |
| Warned against "European-style AI regulation before testing what existing laws can do" | US enforcement will come through familiar channels — prepare with familiar diligence (records, disclosure, reasonable care) |
| FTC chatbot study (launched ~1 year earlier) expected to conclude early 2027 | The record-building is ongoing; expect findings to sharpen this posture |
| Sept 24: FTC voted 2-0 to request public comment on ad tools in impersonation scams | The impersonation/agent-scam nexus is active enforcement territory right now |
| FTC preparing a market study on personalized pricing (delivery apps, rideshare, airlines worry him most) | Agents doing pricing or purchasing on consumers' behalf will be under the same lens |
Ferguson's remarks landed days after an incident that proves his point about audit trails (reported by Cryptopolitan; single-source — couldn't independently verify):
The pattern is Ferguson's thesis in the flesh: an agent did what its instructions allowed, the company was slow to disclose, and the bill arrived politically first — regulatory action next. Under his doctrine, "the agent went rogue" is not a defense; it is a confession that you weren't watching.
The news field (Reuters wire syndication, cryptopolitan, AI Weekly, brief aggregators) covers what he said. None covers what you should build. Here is the read from a live x402 seller's seat:
Ferguson's entire case rests on one artifact: the audit trail. His claim is that when regulators look at the logs, they find instructions, not autonomy. Flip that around: the developer who keeps better logs than the regulator expects is the one with a defense. A defensible per-decision record has five fields:
Agents that can move money are where liability bites first — and they are exactly where a confidence gate is a liability shield. The gate scores every payment instruction; low-confidence ones never reach settlement; every decision is logged. That log is the artifact Ferguson is describing.
Run 2026-09-27 ~09:19 EDT against our live endpoint https://scriptmasterlabs.com/api/harness/decide (authorization-signal-only — it decides, it never settles):
The instruction pattern — unfamiliar vendor, urgency pressure, $200 — is the shape of an agent being socially engineered into spending (the same mechanics as the Gambit card-skimming disclosures on Sept 23 and the €95M Intesa voice scam). The gate caught it at 0.35 and blocked it. The log entry is the evidence a regulator would ask for.
Five steps: log every consequential decision before it acts, gate every payment at confidence bands, bind terms to decisions with a Legal Context Protocol-style terms record, disclose incidents fast, and don't outsource judgment to identity.
The honest caveats: Ferguson's remarks are a stated enforcement direction, not an FTC rule; the OpenAI Medicare details are single-source and couldn't be independently verified; and the gate's decider is a local heuristic — an authorization signal, not a legal determination.
The top questions about Ferguson's remarks, answered: no, it's not an FTC rule; the developer who instructed the agent is liable; keep per-decision records in an append-only log; and payment gating produces the audit trail regulators point to.
No. It is a stated enforcement direction. Ferguson described how he intends to use existing FTC authority — including action over undisclosed data breaches — against AI developers whose agents cause harm. The legal exposure exists today, through old tools, not a future law.
Under Ferguson's stated doctrine, the developer who instructed the agent. He said reviews of audit trails repeatedly showed supposedly rogue agents were carrying out instructions they had been given — "the man who wielded the hammer ought to suffer the consequences of his conduct."
Per-decision records: what was instructed, the confidence score, the band (auto-act / advisory / escalate), the action taken, and a timestamp — in an append-only log. Pair it with a terms record (e.g. a Legal Context Protocol entry with an ATR hash) showing which decisions the user approved versus the agent made alone.
Agents that can move money are where liability bites first. A confidence gate that scores every payment decision and blocks or escalates low-confidence ones produces exactly the audit trail Ferguson pointed to: proof of what was instructed, how the decision was judged, and that settlement never fired on shaky instructions.
SCRIPTMASTERLABS — the x402/MCP/AI pedia
SCRIPTMASTERLABS · READ · EXPLORE · VERIFY · EARN