QWE AI Academy Here’s the twist almost nobody led with: under the Amazon vs. Perplexity – U.S. Court of Appeals for the Ninth Circuit ruling, the AI company didn’t “hack” Amazon – you did. On August 4, 2026 the panel vacated the March preliminary injunction that had tried to keep Perplexity’s Comet Assistant out of Amazon accounts. The court said the human user is the one who accesses Amazon’s computers; the Assistant is just a tool.
So what? Agentic shopping isn’t frozen by that injunction anymore in the Ninth Circuit. Remand continues. En banc rehearing was later denied. If you want Comet to line up coffee filters or a gift card, the fog is thin enough to act – if you keep irreversible clicks human.
The problem: platforms treat your agent like a stranger
You log into Amazon. You ask an AI browser for the cheapest 12-pack of paper towels in your size and a cart drop. Same session you’d run by hand. Amazon treated it like automated entry into password-protected space and sued under the federal Computer Fraud and Abuse Act (CFAA) and California’s CDAFA.
March 2026: Northern District of California entered a preliminary injunction. Reuters covered the stay, the June 11, 2026 argument, and the August 4 vacatur – the first major appeals fight over whether an agent for a logged-in user is still “the user.”
Existing advice is thin. “Never use agents” throws away why you wanted the browser. Waiting for a full trial leaves working tools idle. Full autopilot – “buy whatever” – walks straight into ToS friction, CAPTCHAs, and bad charges.
What failed before the practical setup
Blind “let it checkout” flows. No spending cap. No stop-at-cart rule. People also copied cloud-side bot patterns that never matched the record the Ninth Circuit actually reviewed. Those habits still hurt even when the preliminary ban is gone.
The catch is legal clearance on one statute prong is not the same as a green checkout button every time.
Recommended approach: Comet with supervised Amazon shopping
Use the assistant. You keep place-order. Assume Amazon can still slow you down with terms or tech on facts the CFAA access theory didn’t carry here.
1. Install Comet cleanly
From Perplexity’s Comet help center (check the live article; UI labels move):
- Download from comet.perplexity.ai.
- Install on Windows or Mac and finish onboarding.
- Import bookmarks/extensions from Chrome if you want continuity.
- Open Comet Assistant so it can see the current page.
Default-browser status is optional. Email/calendar connectors stay optional for basic Amazon work.
2. Harden the money path before any agent click
- Virtual or single-use card with a hard cap.
- Don’t leave your primary bank card as the only saved method for unattended reuse.
- Amazon 2FA on – surprise logins should still hit your phone.
Who holds the handle? Same question as a power drill in a rental wall. Courts care. Your statement cares more.
3. Prompt for cart, not silent checkout
Starter prompts:
Open Amazon, search for [exact product + brand], filter to [size/color],
compare the top 3 by unit price and recent ratings,
add the best match to my cart, then STOP and show me the cart total.Find a $25 Amazon e-gift card, use Buy Now only after I confirm,
wait for my OTP, do not touch other cart items.Perplexity’s own help examples sound like “Add Caesar salad ingredients to my cart and let me review it before checkout.” That review line is the product. Without it you’re testing luck, not the agent.
4. Confirm in the UI, then check Orders
Watch the steps. CAPTCHA, login wall, payment stall – take over. After any “done,” open Amazon Orders yourself. Mid-flow blocks are normal. They aren’t a bug in the vacatur.
| Risk | Before Aug 4 injunction era | After Ninth Circuit vacatur |
|---|---|---|
| Court ban on Comet Amazon agent | Active (then stayed on appeal) | Vacated; agent may run |
| CFAA “access” claim vs Perplexity on this architecture | District court thought likely | Appeals court: unlikely on current record |
| Amazon ToS / technical blocks | Available | Still available |
| Your payment mistakes | Your problem | Still your problem – use caps |
Scorecard in one line: computer-access law got narrower on this fact pattern. Contract friction and clumsy payments did not.
What the Ninth Circuit actually decided
Read the PDF. Less drama than the headlines. Lots of “access.” Amazon.com Services, LLC v. Perplexity AI, Inc., No. 26-1444 – opinion filed August 4, 2026, injunction vacated, case remanded. Judge Milan D. Smith, Jr., wrote for the panel.
From the official Ninth Circuit opinion:
- CFAA private suits need intentional access without authorization (or exceeding it), information from a protected computer, and loss ≥ $5,000 in a one-year period. The panel stopped once “access” failed and did not finish the other elements.
- Statutory “whoever” points at a person or legal entity – not the software stack.
- On this record the user accesses Amazon. Quote: the Assistant is “a tool, not a person for statutory purposes.”
- Architecture the court described: Comet local browser; Assistant screenshots your view; images go to Perplexity servers; navigation instructions come back. That loop alone is not Perplexity entering Amazon’s servers.
- Same user-not-Perplexity result under CDAFA.
- Equitable factors favored Perplexity after likelihood of success on access collapsed – harm, balance, public interest (consumer choice / nascent tools).
Limits, in the court’s own lane: “We do not establish a new legal regime governing agentic AI.” A footnote says the outcome does not impair Amazon’s ability to regulate access through private terms of service. And the panel left an architecture door open – if a later record shows Perplexity exercising control so the assistant effectively gains entry to Amazon’s servers, the “who accessed” answer can flip.
Think power drill again. The manufacturer doesn’t enter your wall. You do. With a motor’s help.
Suit background, briefly: Amazon filed in November 2025 over Comet Assistant shopping inside password-protected accounts, including fights about how the agent identified itself. Amici such as the Knight First Amendment Institute, ACLU, and EFF warned about overbreadth for research and journalism tools (Knight Institute case page).
Real-world example: restock in under ten minutes
Need dishwasher pods. Same brand as last time. Prime. Under $30.
- Launch Comet. Sign into Amazon in a normal tab – you type the password.
- Assistant prompt: “On Amazon, find [brand] dishwasher pods, the pack size I usually buy, Prime only, under $30. Add one to cart. Do not check out. Paste the cart line items and total here.”
- It navigates, screenshots, follows returned instructions, fills the cart.
- You read the reply, open the cart tab, confirm SKU and price, checkout yourself – or approve one explicit place-order step.
- Save the confirmation number.
That shape matches the opinion’s system story: your browser talks to Amazon; Perplexity sees screenshots and returns guidance. You’re still the accessor.
Pro tip: Dedicated Amazon “agent” browser profile. Virtual card only. No gift-card balance you care about. If detection or ToS enforcement tightens, you lose a sandbox – not your main wallet.
Pro tips that change outcomes
Stay on the blessed fact pattern: local browser, your direction, screenshot loop. Fully cloud-side agents hitting merchant systems without your machine in the middle sit in the bucket the panel refused to regulate in advance.
Friction stays. Amazon can still build blocks and plead contract. CFAA “access” stumbling on this record does not delete those paths – map that once and stop re-litigating it in your head each session.
Docket over headlines. Injunction appeal finished at the panel; as of September 10, 2026 reporting, en banc rehearing was declined with no judge requesting a vote. Northern District of California still has the live case. Other circuits can diverge. Treat the window as usable, not carved into permanent federal policy.
FAQ
Did the Ninth Circuit make all AI shopping agents legal on Amazon?
No. One preliminary injunction. One access theory. Comet’s described architecture. Nothing like a blanket blessing for every bot on every site.
Can Amazon still kick the agent out?
Yes. Picture checkout halfway done, then a block or a flagged session under Amazon’s rules. The opinion’s footnote already preserves private terms-of-service control, and technical measures never depended on this injunction. Keep a human backup – cancelable card, stop-at-cart prompts, Orders tab check. Autopilot is how you learn expensive lessons.
Is the case completely over?
The injunction appeal ended in Perplexity’s favor at the panel, and en banc rehearing was declined per mid-September 2026 coverage. The lawsuit continues on remand. Remaining CFAA elements and non-CFAA theories were not decided once access failed. Other circuits aren’t bound. Use the tool carefully now; don’t bet the company treasury on this opinion never moving again.
Next action: install Comet, issue a capped virtual card, run one cart-only Amazon prompt, and open the order page yourself before any agent ever hits place order.