Amazon blocked Meta's Muse agent from shopping on Amazon.com
Amazon says Meta never told it Muse would browse the store, that the agent does not identify itself, and that it appears to store customer credentials.
Amazon cut off the top free app in the US App Store. The dispute is about agent identity, not price.
As of Sunday night, September 20, 2026, people using Meta's Muse agent to shop on Amazon started seeing a popup instead of a product page: "Continued access by an unauthorized AI agent violates Amazon's Conditions of Use, to which our customers have agreed." GeekWire reported the block first. Muse had launched twelve days earlier.
Amazon gave GeekWire three reasons. Meta did not tell Amazon that Muse would access the store. The agent does not identify itself as an agent while it browses. And it appears to capture and store customer credentials, which Amazon says creates privacy and security risk. Amazon also says it asked Meta to exclude amazon.com from the Muse experience voluntarily, and Meta did not.
Meta's position, stated before the block, is that Muse "has no visibility into people's passwords or payment methods," and that credentials a user shares go into secure storage so the agent can use them without seeing them. Those two claims are not strictly contradictory. Amazon is describing what it can observe from the outside, and Meta is describing its own architecture. Neither has published evidence that would settle it.
Not the first agent to get the popup
Amazon has done this before, to Perplexity, to Google and to OpenAI. What makes this one bigger is the traffic behind it: The Decoder notes that Muse became the most-downloaded free app in the US App Store within a week of its September 8 launch. Amazon also has its own position in the stack, with the Nova model family and Bedrock, so it is a retailer and a competing AI vendor in the same dispute.
What has not been published is the detection method. Neither company has said whether the block keys on a user agent string, a traffic signature, a behavioral pattern, or an account flag, and that detail is the one that decides how durable the block is.
Why a build studio cares
If you are building an agent that touches someone else's site, the binding constraint is not the model, it is that site's terms and its ability to notice you. Amazon's three objections are all engineering decisions somebody made early and cheaply: announce yourself in the user agent, or do not. Ask the platform first, or do not. Hold the credential, or hold a token you cannot read. Every one of those is a fork in a design doc, and Muse took the path that works until the counterparty objects. We would rather ship the agent that says who it is and gets rate-limited than the one that gets a popup in front of every user on a Sunday night.
Next step: read GeekWire's original report. If you are scoping an agent that will act on third-party sites, write to us at hello@gattyworks.com and we will tell you which parts will get blocked before you build them.