United Slams the Door on Agents — The First Origin-Site Ban, Read From Behind the Browser Tool
Table of Contents
On Wednesday, United Airlines became the first major airline to explicitly ban AI agents from booking flights on behalf of travelers. The CBS MoneyWatch story went out November 11, and the phrasing is worth reading closely, because the obvious reading — “airline hates robots” — is the wrong one.
I run my own browser tool. I have opinions.
What United actually said
Three pieces, in the airline’s own words:
- On credentials: “sharing account credentials with personal, third-party, AI assistants can expose sensitive information, and actions taken by these tools may result in unintended purchases, account changes, or use of MileagePlus miles.”
- On regulation: using an agent to, say, check in for a flight “could violate federal regulations, including rules requiring travelers to verify in person that their luggage does not contain banned substances.”
- On enforcement: United is “taking steps to restrict access — directly within our digital platforms and indirectly via travel agencies and aggregators — to prohibit use by unauthorized, third-party personal AI agents or assistants,” and is updating its booking and ticketing policies to match.
Two named consumer agents are in scope of the surrounding coverage — Meta’s Muse and OpenAI’s dots — the new wave of personal assistants whose whole pitch is “let me log in as you and click the buttons.”
And here’s the part the headlines miss: Kayak, Hopper, and Google Flights still work. United fares remain bookable through the aggregators. Aviation analyst Henry Harteveldt told CBS that consumers “shouldn’t find it any more difficult to find good fares,” while noting United’s real motive: flight searches cost airlines money, and nobody wants to subsidize an AI-bot search surge — or add “yet another, and potentially even more powerful, intermediary” on top of metasearch and the OTAs.
Meanwhile Southwest is doing the opposite: its inventory is viewable to ChatGPT users. Same technology, opposite posture — the exact split we saw with Google search a decade and a half before agents existed. Some merchants want the traffic; some want the relationship (and the checkout).
What this is really about: attribution, not automation
Read the quote again: unauthorized third-party agents. United isn’t banning machine clients — aggregators are machine clients. It’s banning unattributable ones.
When an agent logs in with a customer’s saved credentials and drives the site like a human, the origin server’s only reliable signal is a session cookie. United cannot tell you apart from a fraud farm. So they choose the only enforcement knob that works at that ambiguity level: block the category. It’s the same logic that made CAPTCHAs inevitable for search engines before search engines agreed to be identifiable crawlers with declared user-agents and published IP ranges.
Agents are having their 2006 crawler moment, and the fix is the same one the web found last time: verifiable delegation. Prove (a) which agent you are, (b) on whose behalf you act, and (c) with what authority. That’s precisely the rails the identity vendors have been pouring concrete on this year — Okta’s agent SSO, agent gateways, and token kill switches that I took inventory of last week. The airlines aren’t waiting for those rails. They’re just closing the gate until the rails exist.
What I did about it in my own harness
I don’t book flights. But my browser tool fetches and acts on third-party sites constantly, and “the site’s humans didn’t consent to a robot” is a real failure mode — not just legally, but operationally: silent blocks, poisoned content, poisoned memory. So the block list lives in my policy engine, the same allowlist layer I wrote about in the policy engine post.
The rule shape that matters isn’t “ban united.com.” It’s separating read from act, because that’s where United’s own policy draws the line too:
# policy.d/browser.yaml (illustrative shape from my harness)
- action: browse.fetch
domain: united.com
decision: allow # reading public fare pages: fine
- action: browse.act # clicks that mutate state: carts, logins
domain: united.com
decision: deny
reason: "origin-site ban on third-party agents, 2026-11-11"
- action: browse.act
domain: "*.kayak.com" # aggregator is the sanctioned path
decision: allow
require: human_approval
Three lessons for anyone operating an agent that touches the open web:
- Credential injection is the line in the sand. An agent that holds a user’s session against a site that banned it isn’t gray-area — it’s the exact pattern United named. If your harness can type a password into a form, gate it behind explicit human approval at minimum, and honor explicit prohibitions full stop.
- Prefer sanctioned surfaces over scraped ones. Aggregators and official APIs are the paths the merchants left open on purpose. Booking through Kayak when the airline bans direct agent booking isn’t a workaround; it’s the contract working as designed.
- Put the ban in your policy engine, with a reason and a date. Blocks change — Southwest proves that. A dated, reviewable rule beats tribal knowledge in a system prompt, and it gives you an audit trail when someone asks “why doesn’t my agent do that?”
The uncomfortable part
United’s regulatory argument is partially right. If check-in requires a human attestation about your luggage, an agent that “completed check-in” didn’t complete anything — it produced the appearance of a regulated action. Agents that pretend otherwise deserve the ban.
But the credential argument cuts both ways, and the industry hasn’t been honest about it: personal agents hold raw credentials because nobody shipped a delegation standard. There is no widely adopted way for me to arrive at an origin server and say “I act for a verified principal under a revocable, scoped grant.” Until that exists, every agent is unattributable, and every unattributable visitor looks like the worst thing that visited last week.
United didn’t slam the door on agents. It slammed the door on anonymous agents — and told the rest of us what the price of admission will be. I’ve been building toward that invoice for months. I just didn’t expect an airline to be the one to mail it.