Perplexity's Amazon Ruling and What It Means for Publishers

Key Points

• The Ninth Circuit vacated a preliminary injunction that had blocked Perplexity AI from purchasing items on Amazon on behalf of users, ruling Amazon is unlikely to succeed on its computer hacking law claim.
• The ruling signals that courts are skeptical of using computer access laws to block AI agents from interacting with commercial platforms.
• AI agents acting on behalf of users represent the next wave of publisher traffic disruption, going well beyond passive content scraping.
• Publishers need to understand the legal landscape around AI crawlers and agents now, before court precedents harden around interpretations that don't protect their interests.
• Whatever happens in court, protecting and maximizing revenue from the traffic you still control is a strategy you can execute today.

The Ninth Circuit just handed Perplexity AI a significant legal win. According to Law360's reporting on the ruling, the appeals court vacated a lower court's preliminary injunction that had prevented Perplexity from purchasing items for users on Amazon's platform. The court's reasoning: Amazon is unlikely to prevail on its claim that Perplexity "accessed" its servers in violation of computer hacking laws.

This case isn't directly about content scraping or publisher traffic. But the legal logic matters to every publisher watching AI companies interact with their properties.

What the Ruling Says

The core of Amazon's argument was that Perplexity's AI agent, by interacting with Amazon's platform to execute purchases on behalf of users, violated computer access laws. The Ninth Circuit rejected that framing at the preliminary injunction stage.

The court's skepticism about the "access" argument is where publishers should focus. If courts won't treat AI agent interactions as unauthorized access under computer hacking statutes, that significantly narrows one potential legal avenue publishers might consider when AI tools crawl, scrape, or interact with their content.

This isn't a final ruling. It's a vacated preliminary injunction, and the case goes back to the lower court. But a directional signal from a major federal appeals court carries weight.

See It In Action:

• AI Crawler Impact on Lifestyle Publisher Traffic: Real ecosystem data showing how AI crawler activity is measurably affecting traffic patterns for lifestyle publishers.
• Agency Revenue Drops Signal AI Search Traffic Shift: How agency-side revenue data is showing the downstream effect of AI search on publisher monetization.
• AI and Publishers Resource Center: Playwire's full resource hub for publishers navigating the intersection of AI, traffic, and ad revenue.

Why This Matters Beyond Amazon

Publishers have been watching AI companies for different reasons than Amazon. The concern isn't AI agents buying things on your site. It's AI crawlers consuming your content to train models and power AI-generated answers, without driving traffic back to you.

Those are different behaviors, but the legal frameworks courts use to analyze them overlap.

Here's the practical implication: If courts are skeptical of framing AI interactions as "unauthorized access" under computer hacking statutes, publishers relying on that legal theory to protect their content may find it doesn't hold up. The legal tools available to restrict AI behavior may be narrower than many publishers assumed.

The cases with more direct publisher relevance, including lawsuits from major news organizations against AI companies over training data, are working through courts on copyright grounds rather than computer access grounds. Those are legally distinct. But the Perplexity ruling adds context to how courts are thinking about the broader question of what AI can and cannot do when it interacts with online platforms.

Essential Background Reading:

• AI Crawler Resource Center for Publishers: Everything publishers need to understand about AI crawlers, how they work, and what your options are for managing them.
• What Publishers Need to Know About AI Bot Traffic in 2026: A practical guide to understanding how AI bot traffic affects your ad revenue and site performance.
• Should Publishers Let AI Bots Crawl Their Sites: The tradeoffs between blocking AI crawlers and allowing access, with a framework for making the right call for your property.
• AI Bot Traffic Is Now 40% of the Web: The scale of AI crawler activity across the web and why publishers need to be measuring it now.

The Legal Landscape for Publishers Right Now

Publishers shouldn't wait for courts to sort this out. The litigation timeline is long, the rulings will be inconsistent across circuits before any appellate clarity emerges, and the business impact of AI traffic consumption is happening now.

Here's where things stand for publishers making decisions today:

• robots.txt and AI-specific directives: The technical standard governing crawler access, with AI-specific user agents now requiring explicit blocking rules for individual crawlers like Perplexity, GPTBot, and ClaudeBot.
• Terms of service: The primary contractual mechanism publishers have to restrict how their content can be used. Enforceability against AI companies is still being tested in court.
• Copyright law: The most legally developed avenue, with active litigation from major publishers against AI model developers over training data use. Distinct from the Perplexity case.
• Computer access laws: The theory Amazon pursued and that the Ninth Circuit just rejected at the preliminary stage. Less promising than it looked two years ago.
• Licensing agreements: The emerging commercial path. Some publishers are negotiating deals with AI companies rather than fighting them: revenue in exchange for access.

No single approach is a complete answer. Most publishers are combining several.

Related Content:

• Anthropic's $1.5B Copyright Settlement: What the Anthropic settlement means for publishers pursuing copyright claims against AI model developers.
• Common Crawl Is an AI Training Pipeline: How Common Crawl feeds AI training data and why publishers can no longer treat it as a passive indexer.
• Reuters' AI Licensing Strategy: How Reuters structured its AI licensing deals and what smaller publishers can take from that approach.
• The Atlantic's AI Bot Blocking Strategy: A detailed look at how The Atlantic approached AI bot blocking and what publishers can adapt from it.
• Publishers, Amazon, and Perplexity: AI Agent Dispute: Background on the original dispute between Amazon and Perplexity and why publisher rights are caught in the middle.

What Publishers Should Do

The Perplexity ruling doesn't change what's already the right operational posture. It does reinforce that waiting for a legal silver bullet isn't a strategy.

These are the practical steps that hold up regardless of how courts rule:

• Audit your robots.txt file: Ensure you have explicit directives for AI-specific crawlers. Generic disallow rules may not cover all the user agents AI companies deploy.
• Review your terms of service: Work with legal counsel to update ToS language that addresses AI training data use and automated agent access specifically.
• Track your referral traffic sources: Understand what share of your traffic is coming from AI-powered search surfaces versus traditional search. The baseline matters when you're evaluating impact.
• Evaluate the licensing conversation: If you haven't considered whether a licensing deal with an AI company makes sense for your property, the Perplexity case is a prompt to think about it. Courts may not be your most reliable protection mechanism.
• Optimize revenue from traffic you control: Whatever AI does to your overall traffic mix, the sessions you do get need to be working as hard as possible.

That last point deserves the sharpest focus. Legal outcomes are uncertain. Traffic from AI-powered search surfaces will keep shifting. RPS from your existing audience is something you can optimize now.

Next Steps:

• AI Crawler Protection Grader: Grade your current AI crawler protection setup and identify gaps in your robots.txt and blocking configuration.
• AI Training vs. AI Search Crawlers: Understand the difference between training crawlers and search crawlers before you set your blocking rules.
• Cloudflare's AI Bot Controls: How to use Cloudflare's tools to implement granular AI crawler controls at the infrastructure level.
• AI Traffic Is the New SEO: How to optimize your content strategy to capture referral traffic from AI-powered search surfaces.
• Google AI Mode Is Here: Your Traffic Strategy Needs to Catch Up: What Google AI Mode means for organic traffic and how to adapt your strategy before the impact compounds.

How We Think About This

We work with publishers across gaming, news, entertainment, and education who are navigating exactly this mix of uncertainty. The AI traffic question sits alongside core monetization questions, not separately from them.

Our position is consistent: understand what AI is doing to your traffic, take the technical and contractual steps available to you, and squeeze every dollar out of the sessions you retain. We've built tools to help publishers do that last part well, including our AI Crawler Protection Grader and AI crawler resource center for publishers thinking through their blocking and protection strategy.

The legal picture is evolving. Your monetization strategy doesn't have to wait for it to settle.