Starting last Sunday evening, anyone trying to let Meta's new AI agent Muse shop for them on Amazon got the same message: blocked, for violating Amazon's terms of service against "unauthorized AI agents." It's a small headline about a shopping bot getting cut off. It's actually a preview of how the internet is going to fight over agents for the next few years.
What Happened
Meta launched Muse on September 8th as a general-purpose task agent — it can handle email, calendars, dining reservations, payments, and shopping, all from one interface. It took off fast, becoming the top free app on Apple's App Store, ahead of ChatGPT.
Less than two weeks later, Amazon cut it off. Users who tried to have Muse complete a purchase on Amazon's site were met with a block screen instead of a checkout page.
Amazon's Case
Amazon's position is that Meta never asked for permission to send an AI agent onto its platform on users' behalf. Beyond that, Amazon raised three specific complaints: Muse doesn't identify itself while browsing, it isn't transparent about what it's doing, and it appears to store user account credentials — which Amazon says creates privacy and security risk for the people using it.
Amazon's stated principle is simple: "third-party applications acting on consumers' behalf should operate openly and transparently." In other words, if an agent is going to act as you, Amazon wants to know it's an agent, not a person, and wants some accountability for what it does with your login.
Meta Pushes Back
Meta's response is that the security concern is overstated. According to Meta, Muse cannot read plaintext passwords or payment information — credentials are stored securely, and even though Muse can use them to log in, it can't view them, including passwords a user types directly into the browser themselves.
So you've got two companies with two different definitions of "safe": Amazon says an agent that stores your credentials and doesn't announce itself is inherently risky, no matter how it's engineered. Meta says the engineering is the whole point — the agent can act without ever exposing the sensitive data to itself, let alone to Meta's servers.
This Isn't Amazon's First Agent Fight
This is also not a new fight for Amazon. It already sued Perplexity over a nearly identical setup — an AI agent shopping on Amazon on a user's behalf — and lost on appeal in August, on federal anti-hacking law grounds. That loss matters here: it suggests Amazon's legal footing to actually stop agents like Muse by force is shakier than its terms-of-service language implies. Blocking access at the platform level, rather than suing, may be the more durable tool Amazon actually has.
Zoom out and the pattern is clear. As AI agents get good enough to act on your behalf across the web — buying things, booking things, managing accounts — the platforms those agents touch are going to start drawing lines about who gets to come in, under what name, and with what access to your credentials. Amazon vs. Meta is round two. It won't be the last round.
The bigger picture
Amazon and Meta are arguing over who gets to send an agent through the door. Underneath that is a quieter shift: more buying decisions now start with an agent or an assistant, and the person only sees what it brings back.
If you sell something, that changes what being found means. The agent reads what it can reach, weighs the sources it trusts, and names a short list. Nobody gets to configure that from outside. What you can do is check which pages the engines read when a buyer asks about your category, and whether your company is in the answer at all.
ClawWorld runs AI visibility work for B2B startups. Start with a free baseline report: 10 buyer questions, who ChatGPT and Claude name instead of you, and the pages they cite.