What is the Amazon vs Perplexity AI agent ruling? The Amazon vs Perplexity AI agent ruling is a federal appellate decision issued on August 4, 2026, in which the Ninth Circuit held that when a person directs an AI agent to browse a website, it is the user, not the AI company, who "accesses" that website under the Computer Fraud and Abuse Act. For commercial real estate professionals, it is the first appellate answer to a question that has quietly stalled AI agent CRE data access since agentic browsers arrived: is pointing an AI browser agent at CoStar, LoopNet, or Crexi a federal computer crime? For the wider picture, see our complete guide to AI tools for real estate investors.
Key Takeaways
- The Ninth Circuit vacated Amazon's injunction against Perplexity's Comet browser on August 4, 2026, holding the user, not the AI vendor, accesses the site.
- The court called an AI agent a tool, not a person, so the Computer Fraud and Abuse Act's "whoever accesses" language does not reach the vendor.
- Judges applied the rule of lenity and warned that Amazon's theory could expose ordinary users to criminal liability for simply running an AI browser.
- A footnote preserves the constraint that actually binds CRE firms: platforms like CoStar and Crexi can still restrict access through private terms of service.
- The ruling is preliminary, binds only the Ninth Circuit, and expressly declines to create a general legal regime for agentic AI.
What the Ninth Circuit Actually Held on AI Agent Access
The panel held that Amazon is unlikely to succeed in showing that Perplexity "accessed" Amazon's computers, and it vacated the preliminary injunction that a district court entered against Comet's shopping agent in March 2026, an order the Ninth Circuit had already stayed pending appeal. The case is Amazon.com Services, LLC v. Perplexity AI, Inc., No. 26-1444, and Judge Milan D. Smith, Jr. wrote for a panel that also included Judge Eric C. Tung and District Judge John C. Hinderaker, as Courthouse News reported.
The mechanics matter more than the headline. Comet runs locally on the user's own machine. When the Assistant works inside Amazon.com, the browser requests the page, the Assistant reads what is already displayed on the user's screen, and it sends screenshots back to Perplexity's servers for instructions. Perplexity's servers never touch Amazon's servers. On that record the court concluded that it is the user who accesses Amazon's computers, using the Assistant as a tool to carry out specific tasks.
Two further points give the decision teeth. First, the statute punishes "whoever" intentionally accesses a protected computer, and the published opinion reasons that however advanced the Assistant is, it remains "a tool, not a person for statutory purposes." Second, the panel applied the rule of lenity, because the Computer Fraud and Abuse Act is primarily a criminal statute. It noted that Amazon's reading could expose users themselves to criminal liability on conspiracy or aiding and abetting theories for the ordinary act of running an AI browser. California's state analogue, the Comprehensive Computer Data Access and Fraud Act, failed for the same reason.
Why AI Agent CRE Data Access Just Got Less Risky
For commercial real estate, the most severe legal theory against agent-assisted research just got considerably weaker. Nearly every valuable data set in CRE sits behind a login: CoStar, LoopNet, Crexi, the local MLS or CIE, Yardi, RealPage, county assessor portals, lender portals, and virtual deal rooms. The Computer Fraud and Abuse Act was the statute that made counsel say no.
That caution was rational. The statute carries criminal exposure plus a private right of action for any plaintiff showing at least $5,000 in loss over a one year period, a threshold a large data vendor clears simply by paying engineers to detect and block agents. When the worst case is a federal computer crime, most acquisitions teams never start. The adoption data reflects that gap: 92% of corporate occupiers have initiated AI programs, yet only 5% report achieving most of their AI program goals. Our walkthrough of AI browser agents for CRE research covers what these workflows look like day to day.
The Ninth Circuit's answer, on this record, is that a Comet, ChatGPT, or Claude agent reading a page your own credentials already loaded is not the vendor breaking into anything. That logic maps directly onto a broker pulling lease comps or an analyst reading a rent roll. If you may legitimately view a page, having software read it for you does not convert your subscription into a hacking case against the AI company. For teams that would rather build on sanctioned pipes than screen scraping, our guide on connecting Claude to CoStar and Yardi data remains the lower risk route.
The Limit That Matters Most: Your Contract Still Binds You
Do not read this ruling as permission. The single most important sentence for CRE sits in a footnote: the outcome does not impair Amazon's ability to regulate access to its site through private terms of service. The court took away the federal hacking hammer and left the contract completely intact.
That is the exposure CRE firms actually carry. A CoStar or Crexi subscription is a negotiated agreement, and most CRE data licenses expressly prohibit automated extraction, bulk downloading, and sharing licensed data with third parties. Breaching those terms will not put you in federal court on a computer fraud charge, but it can trigger account termination, license revocation, and breach of contract claims. For a firm that runs its NOI, cap rate, and DSCR analysis on platform comps, losing data access in the middle of a deal is the far more realistic disaster.
Platforms also keep every technical defense. A recurring theme in the litigation was Perplexity's decision not to send a user agent string identifying that an AI agent was active, a signal that would have let Amazon block it. Expect CRE data vendors to demand that disclosure and to throttle or block accordingly. This is the same access control trend we covered when Cloudflare began blocking AI crawlers by default. For personalized guidance on setting an AI data policy that keeps your vendor relationships intact, connect with The AI Consulting Network.
What CRE Firms Should Do Now
The decision is preliminary, it binds only the Ninth Circuit, and the panel went out of its way to say it does not establish a new legal regime governing agentic AI and does not address tort claims. The case now returns to the district court. With that framing, five concrete steps:
- Read your data licenses first. Pull the current terms for CoStar, LoopNet, Crexi, your MLS or CIE, and Yardi. The automated access clause, not the federal statute, now defines your real exposure.
- Separate reading from extracting. Letting an agent summarize a page you already opened is a different act from harvesting a database in bulk. License terms target the second one.
- Prefer sanctioned pipes. Vendor APIs, official integrations, and licensed feeds carry contractual permission. Screen scraping never will.
- Write an internal policy. Decide which platforms your team may point an agent at and record it, before a junior analyst decides on your behalf.
- Keep humans on the numbers. An agent that misreads a rent roll produces a wrong NOI, a wrong cap rate, and a wrong offer. Verify every extracted figure against the source document.
CRE investors who want help drawing the line between useful automation and contractual trouble can reach out to Avi Hacker, J.D. at The AI Consulting Network.
Frequently Asked Questions
Q: Does this ruling mean I can point an AI agent at CoStar?
A: Not automatically. The decision makes a Computer Fraud and Abuse Act claim against the AI vendor unlikely on similar facts, but it expressly leaves platform terms of service fully enforceable. Check your subscription agreement before pointing any agent at licensed CRE data.
Q: Is the Amazon vs Perplexity decision final?
A: No. The Ninth Circuit vacated a preliminary injunction and remanded for further proceedings, so the underlying lawsuit continues. Amazon may also seek rehearing or ask the Supreme Court to review the decision.
Q: Does the ruling apply outside the Ninth Circuit?
A: It binds federal courts in the Ninth Circuit, covering California, Washington, Oregon, Nevada, Arizona, Idaho, Montana, Alaska, and Hawaii. Courts elsewhere may find the reasoning persuasive, but they are not obligated to follow it.
Q: What is the biggest AI agent risk for a CRE firm right now?
A: Contract risk, not criminal risk. Violating an automated access clause can cost you account termination and license revocation, which is both more likely than a federal claim and more disruptive to an active pipeline.
Q: How should a smaller CRE firm respond to this ruling?
A: Start with sanctioned integrations and a short written policy naming which platforms agents may touch. If you want that mapped against your actual tool stack, The AI Consulting Network specializes in exactly this kind of implementation and governance work.