The encounter between Amazon and artificial intelligence agents raises a question that also concerns shoppers: when we entrust a purchase to an assistant, who decides which steps it can take? Radar Special 13A follows the Amazon–Perplexity case to understand how the customer’s delegated authority, shop rules and the freedom to choose one’s intermediary come together.
Amazon and agents — Who decides for whom?
Special Issue 13A | Wednesday 11 November 2026 | Approximately 7 minutes to read
“Find comfortable headphones for video calls. I do not want to spend more than eighty euros. Show them to me before buying.” We want to save time searching and keep the final decision for ourselves. If the headphones arrived straight at home, even within the eighty-euro limit, our go-ahead for the purchase would be precisely what was missing.
With an agent, we can also entrust some operational steps to the system: through an AI model and the available tools, it can consult pages, compare offers and prepare an order. This makes the process more convenient, but requires our instructions to accompany every step. In the case of the headphones, doing the job well also means stopping, showing us the proposal and waiting for us to decide.
1. The shop, the assistant and the customer
In its statement on Perplexity, Amazon argues that assistants buying on customers’ behalf must identify themselves openly and respect the shop’s decision on whether to participate. The dispute concerns the Comet browser’s assistant and its access to the site: it does not represent a rejection of AI as such. The company’s reasons, including the harms it alleges, remain the claims of one party.
The legal proceedings then changed direction. On 4 August 2026, the US Court of Appeals for the Ninth Circuit vacated the preliminary injunction and remanded the case to the district court. On the facts examined, it considered the assistant a tool through which the user accessed Amazon’s systems, finding the claims under the cited US laws unlikely to succeed.
This step is important, but has a precise scope. It does not resolve every possible liability or authorise any agent to enter anywhere. Understanding the case requires considering the decisions made, the contractual terms and how the service actually works together.
2. When Amazon buys from other shops
Amazon itself offers tools for buying outside its own store. The Shop Direct documentation describes two routes: customers can visit the merchant’s site or, for some eligible products, use Buy for Me and ask Amazon to complete the purchase on their behalf. The service’s existence does not mean that every product and every shop is included.
Two integrations that look similar may have different agreements and requirements. This is precisely the difference that should be made understandable: which security conditions are required of an assistant? Can an external provider meet them? And can the customer choose a tool that compares several shops before guiding them towards an offer?
🧠 Radar Insight — Where does the advice come from?
A shop’s assistant may know the catalogue and procedures well; an external one may broaden the comparison. Neither position alone guarantees independent advice. To assess it, we should look at the alternatives considered, those excluded and any economic benefits linked to the choice. These are questions about the service, not accusations already proved.
3. Eighty euros is not the whole assignment
Let us return to the headphones. Does the limit include delivery? Must the product be new? Can the assistant substitute a model or choose another seller? Clarifying these conditions makes the choice the customer is entrusting to the machine identifiable. As we saw when discussing delegating spending authority to AI agents, being able to enter an account and having permission to spend are two different things.
Authentication verifies who is using the account; authorisation establishes which actions they can take. The work begun by NIST on agent identity and authority addresses these very problems. It does not certify products on the market: it helps identify controls that must then work in the actual application.
The customer can confirm each order or authorise a purchase in advance within explicit limits. In both cases, they must be able to understand the assignment, check its conditions and revoke it for future actions. The service, in turn, must prevent the limit from being exceeded: relying on the model to remember a sentence from the conversation is not enough.
4. Keeping evidence of the yes
With the Agent Payments Protocol, or AP2, Google proposed a way to document delegated authority through cryptographically signed mandates. The initial mandate describes intention and conditions; the cart mandate concerns the items and price of the order. The proposal distinguishes between confirmation by a customer who is present and an assignment authorised in advance.
A signature can help verify the origin and integrity of that record, but cannot demonstrate that the offer was good value or that every condition was understood. The headphones may cost less than eighty euros and still be the wrong ones. This is why evidence of authorisation must be accompanied by clear information before the purchase. AP2 is a technical proposal, not a law or a solution adopted everywhere.
💡 Did you know? — A page cannot change the mandate
An agent may encounter hostile instructions within a page it is consulting: this is the problem of prompt injection. Text inviting it to ignore the budget does not acquire authority simply because the machine reads it. Controls on amounts, operations and data recipients must be able to stop an action even when the model proposes it.
5. Convenience must keep the choice visible
If a purchase goes wrong, the customer must be able to reconstruct what they asked for, which offer was chosen and which operation was initiated. If the seller, assistant and payment service each describe only their own stage, the burden falls on the person who paid. Keeping proportionate, understandable records makes it possible to challenge a transaction without collecting the person’s entire digital life.
It is the same criterion that guides checking responsibilities and the ability to intervene: a useful service leaves room for oversight even after the result. Both the shop’s security and the freedom to choose an intermediary deserve attention. Neither belonging to the platform nor being an external assistant is enough to guarantee them.
The headphones arrive and the task seems complete. But can we understand why they were chosen, challenge an error and stop subsequent purchases? Delegating authority truly saves us work when it preserves these possibilities, together with an understanding of what we have decided.
Read the full issue
The dossier reconstructs the Amazon–Perplexity dispute and explores authorisations, payments, data access, responsibilities and freedom of choice, distinguishing the US case from the European framework. Primary sources are collected in the final pages.
© 2026 Barbara Gattobigio · Gruppo Radar
Comprendere oggi. Costruire domani · by effettoantropico.life
All rights reserved on original content. Free access does not authorise reproduction or republication without consent, except as permitted by law. Third-party materials remain the property of their respective owners. To share this issue, use the link to the article.
Cover in focus





