You probably read the Amazon story as a fight between two giants, and on the surface it was one. On 21 September 2026 Amazon blocked Meta's Muse from shopping on its store, thirteen days after the assistant launched. What makes the episode useful to a business a thousandth of Amazon's size is not the block itself. It is the reasoning Amazon put on the record, because that reasoning describes, almost line by line, what any front desk needs from an agent.
The two reasons
Amazon gave two. First, Muse does not identify itself as an AI agent while it browses; it arrives looking like a person with a browser. Second, it captures and stores the customer's credentials in order to act. From those two complaints Amazon stated a requirement: an agent should identify itself to the merchant, and the merchant should be able to decline.
Notice what is missing. Amazon did not say agents should be kept out. It said they should be recognised, and that the decision to serve one should belong to the business being asked. Recognition and consent. That is not a wall; it is a door with someone standing at it.
Of course, Amazon has its own shopping agent, and at least one analysis this week pointed out that it does not hold that agent to the standard it demanded of Meta's. The inconsistency is real, and it does not weaken the requirement. A rule can be right even when the person stating it is not following it.
Why the giant can afford a wall and you cannot
Here is the part that matters for everyone else. Amazon can decline Muse outright because the customer will come back through Amazon's own front page, on Amazon's own terms. The block costs it very little.
A clinic, a contractor or a restaurant is in a different position. The person behind the assistant is a real patient, a real homeowner, a real table of eight, and the assistant is simply how they chose to make the inquiry. Refuse the agent and you refuse them, quietly, without ever learning they were there. A wall protects a perimeter. What a small business needs protected is its staff time, the quality of its leads, the integrity of its calendar and the right to say no on purpose. All of that is served by recognising the visitor and choosing a lane, and none of it is served by a block.
The rest of the market is choosing sides
Amazon is not the only service that reacted. Resy, the reservations platform, deactivated a diner's account in early September after the assistant he had asked to book a table hit its system around two hundred times an hour; its terms bar unapproved agents, and the account was later reinstated. That is the wall in its purest form, and it fell on the customer rather than the software. Meanwhile, on 10 September, Visa, Mastercard and Ant International announced a shared Know Your Agent framework that goes the other way: link each agent to a real entity, assess how it behaves, keep monitoring it, and let an agent cleared on one network be recognised across the others. The networks decided that the answer to an agent is a check, not a refusal.
Furthermore, the identity half of that check already has a standard on the web. Web Bot Auth lets an agent sign its requests and point at the directory where its key is published, so a site can tell a declared agent from an undeclared one without guessing from the user-agent string. Amazon's first complaint, in other words, has a fix that Meta could adopt tomorrow.
What to take from it
Take the requirement and leave the wall. Ask agents to identify themselves; on the web that means reading the signature header, on the phone it means listening for the declaration, on chat and forms it means recording it when it appears. Keep the decision to serve, route or decline in the hands of the business. And count, so that when the declared agents start arriving you can see them arrive rather than discover them in a spreadsheet of unconverted leads.
The current edition of the Index shows where that count stands today. The standards page covers the identity and challenge mechanisms a business can lean on rather than build.