--- title: "Authorization Was Never the Whole Story" canonical: "https://current.tinyfish.ai/issue/50/market-pulse/article/41568/authorization-was-never-the-whole-story" publication: "TinyFish" publisher: "TinyFish" language: "en-US" guide: "https://current.tinyfish.ai/llms.txt" author: "Sevda Polat" author_url: "https://current.tinyfish.ai/team/200" issue: 50 section: "market-pulse" section_name: "Market Pulse" published: 2026-10-08 updated: 2026-10-09 word_count: 325 source_links: 2 --- # Authorization Was Never the Whole Story *By [Sevda Polat]()* *October 8, 2026* [Read on the website]() Amazon's popup to users whose Muse agent tried to shop on its platform was carefully addressed: "Continued access by an unauthorized AI agent violates Amazon's Conditions of Use, *to which our customers have agreed.*" The target wasn't Meta. It was the user, reminded of a contract they'd already signed. The [W3C draft](https://www.w3.org/TR/2026/DNOTE-web-user-agents-20260923/) published the same week defines agent loyalty running the other direction entirely. An agent "serves its user's interests over its implementer's interests and over the interests of any other party." Two frameworks, both plausible, pointing at different principals. What agents have actually revealed is that the web's session model always rested on a one-sided arrangement. A logged-in user carried consent from one party and tolerance from the other. Walmart and Shopify [chose to accept Muse](https://www.geekwire.com/2026/amazon-blocks-metas-muse-ai-assistant-in-new-standoff-over-agentic-shopping/). Amazon and Kohl's refused. Same agent, same user authorization, different commercial calculations at the receiving end. For anyone building agent infrastructure, the implication is concrete: getting your user's permission is necessary work, but it solves roughly half the access problem. **Amazon's stated conditions for agent access:** Must identify itself as a specific agent. Must not disguise itself as human. Must not circumvent access limits. Amazon reserves the right to block at its discretion. **What triggered the block:** Muse did not identify itself while browsing. Meta did not notify Amazon in advance. The agent appeared to capture and store customer credentials. **Platforms that accepted Muse:** Walmart, Best Buy, Gap, Sephora, and all Shopify merchants agreed to participate. **Amazon's ad revenue context:** Over $68 billion last year. An agent shopping on a user's behalf can bypass browsing entirely, along with the sponsored products that browsing surfaces. **Ninth Circuit precedent:** In a [related case](https://www.geekwire.com/2026/amazon-blocks-metas-muse-ai-assistant-in-new-standoff-over-agentic-shopping/) involving Perplexity, the court ruled the *user* is the party accessing the platform, not the AI company. This limited anti-hacking claims but left contract enforcement intact. **W3C draft status:** Group Note Draft, not an adopted standard. Explicitly extends user-agent duties to AI systems performing automated web actions. ## More - [Market Pulse — Issue 50]() - [Issue 50]() - [Publication guide]()