Amazon v. Perplexity is the first big court test of whether a store can stop an AI agent from shopping for a logged-in customer. Amazon sued Perplexity in November 2025 over its Comet browser agent and won a preliminary injunction on March 9, 2026. According to later reports, the Ninth Circuit reversed that injunction on August 4, 2026, reasoning that it is the user, not the AI company, who accesses Amazon's computers. Amazon filed an amended complaint in September, and the case continues as of November 2026.

This explainer is based on court coverage; we have not read every filing ourselves, and the appellate steps are attributed to press reports.

What is Comet and why did Amazon sue?

Comet is Perplexity's AI web browser with a built-in agent, Comet Assistant. It launched on July 9, 2025, and became free. It can browse sites, fill in forms and add items to a cart while you're signed in, including on Amazon.

Amazon's complaint argued that Comet accessed customers' Amazon accounts without Amazon's authorisation, violating the federal Computer Fraud and Abuse Act (CFAA) and California's computer-fraud statute. Amazon's later filings add that Comet sent a standard Chrome user-agent string instead of identifying itself, which Amazon's Agent Terms require since May 2025.

That last hop is central. Amazon alleges that Comet for iOS copied users' Amazon session cookies to Perplexity's cloud servers, which then requested Amazon pages directly (TNW).

Amazon v. Perplexity timeline

  1. Amazon adds Agent Terms to its Conditions of Use
  2. Perplexity launches Comet
  3. Amazon sues Perplexity over Comet
  4. Judge Maxine Chesney (N.D. Cal.) grants Amazon a preliminary injunction
  5. Perplexity appeals to the Ninth Circuit
  6. Perplexity says it has temporarily disabled Comet's assistant on Amazon for iOS
  7. Ninth Circuit reportedly reverses the injunction
  8. Ninth Circuit reportedly denies Amazon's rehearing request
  9. Amazon files a 41-page amended complaint

The March 9 ruling date and the court are confirmed by Search Engine Journal and GeekWire (whose article is dated March 10, the day after the ruling). The August, September and amended-complaint entries come from TNW's reporting; we have not read the appellate opinion directly.

What did each side argue?

Amazon's position

  • Comet accessed Amazon accounts without Amazon's permission, which Amazon says is unauthorised access under the CFAA, even if the customer agreed.
  • Comet disguised itself as Chrome, and Amazon alleges Perplexity changed the user-agent each time Amazon built detection.
  • The traffic created security risk and cost. Amazon's amended complaint says eight traffic engineers spent at least 1,280 hours on the agent since July 2025, and that Comet ran at least 185,712 sessions on Amazon.com as of June 15, 2026. It seeks damages "well above" $260,000.

Amazon also points out that Cloudflare reported in August 2025 that Perplexity used an undeclared crawler that impersonated Chrome, and removed it from its verified-operators list.

Perplexity's position

  • The shopper is the one accessing their own Amazon account, and Comet is just a tool the shopper chose, like a browser.
  • Amazon wants to ban AI assistants on its site to protect its advertising and its own agents.
  • In appellate briefs, Perplexity said "no Perplexity computer ever has direct access to an Amazon computer." Amazon disputed that statement in a May 6, 2026 letter, according to TNW.

Pros

  • Perplexity: users should pick their own tools, including AI agents
  • Perplexity: the Ninth Circuit reportedly agreed the user is the one accessing

Cons

  • Amazon: undeclared agents undermine fraud detection and account security
  • Amazon: copying session cookies to a third-party cloud goes beyond a browser

What did the Ninth Circuit decide?

According to TNW, on August 4, 2026 the Ninth Circuit reversed the preliminary injunction, holding that under federal anti-hacking law the user, not the AI company, accesses Amazon's computers. It reportedly denied Amazon's rehearing request on September 10.

That reasoning, if it stands, weakens a store's ability to treat an agent working inside a customer's own logged-in session as a hacker. It does not decide the whole case. Amazon's amended complaint adds claims under the California computer data access statute and for tortious interference with contract, and focuses on the cloud-server copying of session cookies, which is harder to describe as the user acting alone.

What does Amazon v. Perplexity mean for shoppers?

In the short term

Comet sessions on Amazon.com cited by Amazon (to Jun 15, 2026)
185,712
Preliminary injunction granted
Mar 9, 2026
Injunction reversed, per reports
Aug 4, 2026
Case status, Nov 2026
Unresolved
  • Don't rely on outside agents for Amazon. Even with the injunction gone, Amazon can still block agent traffic it detects, as it did with Meta Muse on September 20, 2026.
  • You are not the defendant. Amazon sued Perplexity, not Comet users. The realistic risk to you is a blocked session or account restrictions under Amazon's terms.
  • Amazon's own agents are the supported path. Alexa for Shopping can watch prices and buy at a target price.

In the longer term

The case asks whether a store can choose which software its customers use. If courts settle on the user-access view, stores will lean harder on terms of use and technical identity checks. That is where standards such as Cloudflare's signed agents and Web Bot Auth come in: they let an agent prove who operates it, so stores can welcome known agents instead of guessing.

For merchants deciding how to treat agents, our guide on robots.txt for AI shopping agents covers the options. For shoppers, the practical question is still which stores allow AI agents.

Bottom line

Amazon v. Perplexity started as a fight over one browser and became a test of who controls the shopping session. As of November 2026, Amazon won the first round, reportedly lost it on appeal, and is trying again with a narrower complaint. For shoppers, nothing has changed in practice: Amazon still blocks agents it doesn't like, so use outside agents at stores that welcome them. getpersonalaiagents.com tracks this and related disputes in its incidents log.