Twelve days after Meta launched its Muse agent, Amazon blocked it. From the night of September 20, 2026, shoppers who asked Muse to buy something on Amazon got an automated message saying that "continued access by an unauthorized AI agent violates Amazon's Conditions of Use." The dispute is the clearest case so far of a retailer refusing an agent that a customer chose to use, and it sets out the arguments every retailer will have to weigh.
Timeline
| Date | Event |
|---|---|
| 2026-09-08 | Meta launches Muse in the United States |
| Before 2026-09-20 | Amazon asks Meta to remove the agent from its site. Meta declines |
| 2026-09-20, night | Amazon begins blocking Muse from completing purchases on Amazon.com |
| 2026-09-21 | The block is reported publicly |
| 2026-09-23 | At Connect, Meta announces Muse connectors with Walmart, Best Buy, Sephora, and others |
What Each Side Says
| Issue | Amazon | Meta |
|---|---|---|
| Permission | Meta did not tell Amazon that Muse would access its store | The agent acts for a customer who asked it to shop there |
| Identification | The agent does not identify itself when it browses | No public rebuttal on this point in the coverage we reviewed |
| Credentials | Muse appears to capture and store customer credentials, which creates privacy and security risk | Muse never sees passwords or payment methods, which go into secure storage |
| Payment | Not addressed | Muse pays with single-use cards from Link by Stripe |
Amazon's public position, as quoted by MediaPost: "third-party applications that offer to make purchases on behalf of customers from other businesses should operate openly and respect service provider decisions about whether or not to participate."
The Double Standard Question
Amazon runs its own agent that buys from other retailers' websites. Its Buy for Me feature completes purchases on third-party stores from inside the Amazon app. Critics pointed out that Amazon is asking for a standard, identify yourself and respect the retailer's decision, that its own agent has been accused of not meeting. We covered that product in Amazon Buy for Me. Whatever the merits, the position is consistent with Amazon's commercial interest: it sells ads on its own search results, and an outside agent that picks the product removes the shopper from those pages.
Why This Matters Beyond Amazon
Three questions from this dispute apply to any site that sells online.
Does the agent identify itself? A signed, named agent can be allowed, rate-limited, or refused on purpose. An agent that looks like an ordinary browser can only be caught by behaviour, which also catches real customers. The move toward signed agent requests is covered in verified agent trust programs and agent reputation and identity.
Who holds the credentials? Retailers are responsible for account security. An agent that stores a customer's login is a new party in that chain. Meta's answer is that credentials sit in secure storage outside the model and payments use single-use cards.
Who owns the customer relationship? When an agent shops, the retailer's recommendations, sponsored placements, and upsells are not seen. That is the commercial core of the dispute, and it is why retailers with large ad businesses have the most to lose.
What Retailers Are Choosing
| Approach | Example | Trade-off |
|---|---|---|
| Block outside agents | Amazon | Protects on-site ads and data. Loses agent-initiated orders to competitors |
| Connect directly | Walmart, Best Buy, Sephora, Wayfair | Captures agent orders with the retailer's own checkout logic. Requires integration work per platform |
| Connect through a platform | Shopify merchants | Reachable by default with no extra work. Less control over presentation |
| Do nothing | Most sites | The agent uses a browser and may fail on bot challenges, logins, or checkout steps |
Brand Visibility Implications
- Brands that sell mainly on Amazon are invisible to Muse for purchases. If a user asks Muse to buy a product that is only on Amazon, the agent has to find it somewhere else or suggest a substitute. Wider distribution now has a direct effect on agent reach.
- Agent traffic is being routed by retailer policy. The same product can be reachable through Walmart and unreachable through Amazon. Check where your products are listed against the Muse connector list.
- A default block is still a block. Many sites refuse agents by accident through bot protection settings. We wrote about that in Your Bot Protection Is Working. That Is the Problem.
Methodology
This page is built from vendor announcements and launch-week reporting, not from Presenc AI measurements. Primary sources are used wherever one exists, including Meta's Connect 2026 newsroom post and product blog, xAI's news page, and X's Original Content Rewards help page. Where a detail comes only from press coverage, such as TechCrunch on Dots, Bloomberg on Amazon and Muse, or PPC Land on X Ads MCP, the page says so. These products are new and none of the vendors has published independent success rates. Status as of October 1, 2026.
How Presenc AI Helps
Presenc AI's crawl analytics show which AI agents and crawlers reach your site and which are refused, and its tracking shows which retailers assistants send shoppers to for your products.