What the Amazon vs Perplexity Ruling Changed

A federal appeals court vacated a preliminary injunction in Amazon's lawsuit against Perplexity over its Comet browser, marking the first appellate ruling on whether AI agents acting for users may access online platforms. The court found computer-misuse law weak against software a customer chose to run on their own account, leaving contract, trademark, and state-law claims untouched. The ruling distinguishes between crawlers and user-authenticated agents, prompting recommendations for terms of service, identity-based access controls, and rate limits over statutory enforcement.

Amazon sued Perplexity in November 2025 over its Comet browser, pleading the federal Computer Fraud and Abuse Act and California's Comprehensive Computer Data Access and Fraud Act. A district court granted a preliminary injunction in March 2026. The Ninth Circuit stayed it pending appeal, and in August 2026 vacated it. The reasoning is the part worth carrying away. On the record before the panel, the systems were being accessed by Amazon's own customers, signed into their own accounts, using software they had chosen. Perplexity was not the one accessing Amazon. On that basis Amazon was unlikely to prevail on a statute written about unauthorised access. It is the first federal appellate ruling on whether AI agents acting for a user may access an online platform, and the panel was careful to say it was deciding that record rather than announcing a doctrine. It did not say agents are welcome, and it did not say a site has lost control of its own front door. Contract claims were not what the panel found weak. Terms of service, trademark questions and state-law theories are all untouched. A different record with different facts, particularly one where the agent operates at scale rather than for one signed-in customer, could come out differently. The useful summary is narrow and worth stating without decoration: computer-misuse law is a weak instrument against software a customer chose to run on their own account. | Crawler | User's agent | | |---|---|---| | Acting for | Its operator | One signed-in customer | | Scale | Many sites, high volume | One session at a time | | Authenticated | Usually not | As the customer | | Data ends up | In the operator's product | In front of the person who asked | | The ruling's reasoning | Does not apply | Applies | Most blocking rules in the wild do not make this distinction. A blanket refusal of automated access catches a customer's own agent alongside the scraper it was aimed at, and those two are commercially opposite: one is a visitor with a wallet, the other is a cost. Three levers, and none of them are statutes. Terms of service are a contract question, and contract was not the theory that failed here. Identity is the second lever: an agent that signs its requests can be recognised and treated deliberately, which is what HTTP Message Signatures and Web Bot Auth exist for, supported at AWS WAF since November 2025 and at Cloudflare since early 2026. Rate and behaviour limits are the third, and they are the only ones that keep working regardless of what a visitor claims to be. Together they let you decide per class of visitor on purpose. The alternative is deciding by accident, which is what a blanket rule does. The trade-offs of each choice are set out in the crawler allowlist post https://inite.ai/en/blog/ai-crawler-allowlist-2026?utm source=devto&utm medium=syndication&utm campaign=blog-agentic-browsing-after-the-amazon-ruling . Whether agent-mediated customers are worth having is a commercial decision, not a legal one, and it is answerable with your own data. Find out whether that traffic already reaches you. Then check whether your checkout, booking or enquiry flow can actually be completed by software driving a browser as a signed-in customer, and whether any step depends on a person noticing something on a screen. What an agent sees on your site https://inite.ai/en/blog/browser-agent-ready-saas?utm source=devto&utm medium=syndication&utm campaign=blog-agentic-browsing-after-the-amazon-ruling covers the mechanics of that audit. Both failure modes cost money. Silently blocking agent-mediated customers who would have converted turns away business. Letting them arrive and fail halfway through generates support load and a bad impression, which is worse than a clean refusal. It is worth reading this alongside what happened to in-chat checkout. OpenAI pulled back from completing purchases inside ChatGPT on 4 March 2026 and confirmed the retirement on 24 March, after roughly five months live and about a dozen Shopify merchants ever going live. Discovery moved into the assistant; the transaction went back to the merchant's own site. The two events point the same way. Buying inside the assistant lost, and the customer's own agent operating the merchant's site just survived its first appellate test. That makes the merchant's own checkout the surface that matters https://inite.ai/en/analyze?utm source=devto&utm medium=syndication&utm campaign=blog-agentic-browsing-after-the-amazon-ruling , which is the argument made in full in agentic commerce after Instant Checkout https://inite.ai/en/blog/agentic-commerce-after-instant-checkout?utm source=devto&utm medium=syndication&utm campaign=blog-agentic-browsing-after-the-amazon-ruling . Sources: Reuters via Yahoo Finance https://finance.yahoo.com/technology/ai/articles/us-court-overturns-amazon-injunction-135004000.html , Engadget https://www.engadget.com/2230471/perplexity-has-successfully-overturned-amazon-injunction-on-its-ai-shopping-bot/ , PYMNTS on the CFAA narrowing https://www.pymnts.com/news/artificial-intelligence/2026/ninth-circuit-narrows-cfaa-reach-in-perplexity-agentic-commerce-ruling/ , CNBC on the March injunction https://www.cnbc.com/2026/03/10/amazon-wins-court-order-to-block-perplexitys-ai-shopping-agent.html .