What Amazon's Muse Block Tells Builders About Agent Access to Marketplaces

Amazon has blocked Meta's Muse from its marketplace. The stated reasons: Muse did not identify itself as an AI agent while browsing, and it appeared to be storing customer data. Users now see a warning that access by an unauthorized AI agent violates Amazon's terms of service.

This is not the first time Amazon has done this. Before Muse, it blocked agents from Perplexity, Google, and OpenAI. A US appeals court reversed the Perplexity decision and allowed its agent back. That legal precedent has not deterred Amazon from continuing to block agents it considers noncompliant. Meta and Perplexity both remain significant Amazon cloud customers; that relationship did not translate into marketplace access for their agents.

The practical point for builders is not about Amazon specifically. It is about the behavioral line that separates a compliant shopping agent from one that will be blocked.

Both of Amazon's stated objections are behavioral, not categorical. Amazon is not banning AI agents from shopping. It is banning agents that do not disclose what they are and that handle customer data outside agreed terms. An agent that identifies itself and stores nothing it was not explicitly given permission to store clears both objections. Muse did neither.

This matters because the shopping platforms your users want access to are not passive infrastructure. They are active counterparties with their own ToS enforcement. An agent that bypasses disclosure requirements does not gain a competitive edge; it gets blocked and leaves the user with nothing. The conservative design choice, declaring agent identity on every session, storing only what the platform's data agreement permits, is also the one that stays live.

The Perplexity appeals court ruling is worth watching, but builders should not plan around it. Courts move slowly, and a ruling that allows one agent back does not establish a general right of agent access to private marketplaces. The platforms that control the most valuable shopping surfaces will negotiate access on their own terms, and behavioral compliance is the price of entry before any negotiation starts.

For agents built on top of platforms that have their own ToS restrictions, there is a practical checklist: identify the agent in every session header, log what data is handled and where it goes, and have a response ready for the moment the platform's detection system flags the traffic. The block comes without warning. Having the disclosure and data controls already in place is what makes the difference between a quick reinstatement and a support ticket queue.