All Articles
StrategyPublished November 19, 20267 min read

SerpApi Lawsuit: Why Your SERP Data Needs Two Keys

Google's legal dispute with SerpApi proves that depending on a single scraping vendor is an avoidable business risk, and splitting your requests across two independent APIs costs less than paying a single-vendor insurance premium.

Matiss Katanenko

Matiss Katanenko

Co-founder, Honeyb

On this page
SerpApi Lawsuit: Why Your SERP Data Needs Two Keys

The legal war over SERP (search engine results page, or the screen Google paints before your customer clicks anything) data, highlighted by Google's lawsuit against SerpApi, proves that relying on any single scraping provider is a business risk you can no longer afford to take. When your rank tracking, product feeds or AI visibility reporting run through one vendor's proxy network, a courtroom filing or an aggressive anti-bot update turns their legal distraction into your engineering outage.

Google showed an AI Overview on 93% of 1,825 commercial US searches, and 71% of the sources those overviews cited sat outside the query's organic top 10, according to Honeyb's capture on our AI Overview tracker. Losing your data feed for a week means losing sight of the actual sources driving buyer recommendations while your competitors take your place.

Why SERP and AI Search Data Pipelines Need Redundancy

93%

US commercial queries with an AI Overview

Leaving AI Overviews untracked hides the top of the results page across 1,825 commercial US searches.

71%

Cited sources outside the organic top 10

A plain top-10 rank check misses most of the pages Google's AI actually cites.

$10.00

SerpApi per 1,000 with Legal Shield

Insuring a single point of failure on the $150 Production plan costs ten times a $1.00 prepaid check.

$1.00

Honeyb per 1,000 Google rank checks

Prepaid credits never expire and failed captures are free, making a two-vendor setup cheaper than one subscription.

A single legal challenge can disable a $10/1,000 API; a multi-source stack with a $1/1,000 provider gives you resilience for less. Sources: Honeyb, SerpApi.

What the SerpApi Lawsuit Is About and Where It Stands

Google's lawsuit against SerpApi, which alleges that SerpApi circumvented security measures protecting others' copyrighted content in search results (Google), has seen its central claims dismissed twice in early court rounds, shifting the battle from the courtroom to technical countermeasures. The dispute shows that while scraping is legally contested, the immediate operational risk to your pipeline is technical.

The courtroom momentum has leaned away from Google during the initial rounds. After losing key DMCA claims in its initial filing (Search Engine Land), Google revised its complaint to focus on content licensing terms (Search Engine Journal).

That amended complaint was also dismissed, handing Google a second loss in the dispute (Search Engine Roundtable). A dismissal keeps the API online today, yet it forces the vendor to spend executive attention and capital defending its infrastructure.

In response to the pressure, SerpApi announced that it joined the Internet Infrastructure Coalition (i2Coalition) and earned the Trust Seal from the coalition's Ethical Web Data Collection Initiative (Bill Hartzer). Joining an industry coalition signals that scraping vendors now compete on legal posture alongside proxy speed.

Why Single-Vendor Scraping Puts Your Pipeline at Risk

Relying on a single scraping vendor creates an operational risk, because a search engine can deploy technical countermeasures like poisoned results or captcha walls that disable your provider's API, leaving your application without data. When a legal challenge stalls in federal court, those upstream HTML and anti-bot changes turn the vendor's legal distraction into your engineering problem, because their API can return incomplete or altered data without warning.

As Bill Hartzer noted alongside the coalition news, technical countermeasures that alter or poison automated results remain a constant operational hazard (Bill Hartzer). If your sole provider hits a wall of poisoned results or a sudden captcha change, your dashboards go blank until their engineers patch the parser.

You also pay a steep cash premium when a vendor bundles legal defense into your monthly quota. On SerpApi's pricing page, U.S. Legal Shield provides up to $2 million in coverage for the scraping and parsing of search engine data, and it starts on the Production plan at $150 a month for 15,000 searches, or $10 per 1,000 searches (SerpApi).

How API Pricing Reveals the Real Cost of Risk

You can pay one vendor $10 per 1,000 searches to insure a single point of failure, or you can pay $1.00 per 1,000 searches across prepaid providers and remove the single point of failure in code. We built the Honeyb API to run on non-expiring prepaid credits without a monthly subscription, and it is our own product.

Building on AI answer data?

The Honeyb API returns AI search visibility as JSON: which brands each engine named, in what position, with what sentiment and which pages it cited. Raw answers from $1.05 per 1,000, enriched from $2.05 per 1,000, no subscription.

We issue keys within one working day. Tell us your engines and volume.

On the Honeyb pricing page, our SERP API and Rank Tracking API charge $1.00 per 1,000 Google checks at depth 10 with the AI Overview citation included, while the LLM Scraper API captures raw answers from ChatGPT, Google AI Overviews and Google AI Mode at $1.05 per 1,000 delivered answers (Honeyb). If you want brand detection, competitor names, sentiment and classified citations, the AI Visibility API delivers enriched answers at $2.05 per 1,000 on those same engines (Honeyb).

ProviderEntry Price / MinimumPrice per 1,000 (Google SERP / AI)Billing ModelLegal Cover Stated
Honeyb (ours)No subscription (prepaid credits)$1.00 Google rank check; $1.05 raw / $2.05 enriched ChatGPT, AI Overviews, AI ModePrepaid credits, never expireNot stated
SerpApi$150/mo Production for Shield$10.00 ProductionMonthly subscriptionUp to $2M from Production ($150/mo) up
SearchApi$100/mo Production for Guarantee$3.00 ProductionMonthly subscriptionLegal Protection Guarantee from Production ($100/mo)
DataForSEOPrepaid balance$0.60 standard queue; $2.00 live ($4.00 live with async AI Overview)Prepaid balanceNot stated
Bright DataPay as you go$1.50 pay as you goPay as you goNot stated

For teams whose compliance lawyers insist on a written indemnity clause in the contract, SearchApi's pricing page lists its Production plan at $100 a month for 35,000 searches ($3 per 1,000) with a Legal Protection Guarantee (SearchApi), whereas SerpApi's U.S. Legal Shield is included from its Production plan at $150 a month for 15,000 searches (SerpApi). We broke down how SerpApi's speed tiers double and quadruple those rates in our guide to SerpApi pricing.

For raw asynchronous SERP volume where a five-minute queue is fast enough, DataForSEO's pricing page lists its standard queue at $0.60 per 1,000 SERPs and live mode at $2.00 per 1,000, or $4.00 per 1,000 live when loading the asynchronous AI Overview (DataForSEO). If you prefer top-up packs over a monthly plan, Serper sells prepaid credit balances, though unused credits expire after six months (Serper).

If you are scraping conversational engines alongside Google, Bright Data's pricing page lists pay-as-you-go web scraper records at $1.50 per 1,000 for ChatGPT Search, Google AI Mode, Gemini, Perplexity, Copilot and Grok, without a Google AI Overviews scraper or brand sentiment enrichment (Bright Data). We tested how these payloads differ in our comparison of SerpApi alternatives and our review of the best AI search APIs.

Why Single-Vendor Risk Multiplies Across AI Search Engines

Relying on a single vendor becomes even riskier when your pipeline expands beyond Google HTML to conversational answer engines, because official first-party model APIs do not return the live web-search citations or organic layouts that buyers actually see. While an official partner API avoids anti-bot blocks, it gives you raw model completions rather than the search-augmented consumer interface, so monitoring real buyer answers across ChatGPT, Perplexity and Google AI Mode requires browser-based scraping providers with a backup key ready when an engine updates its layout.

Honeyb ran 20 buyer-intent prompts three times each through four engine APIs and found that the top recommended brand changed between back-to-back identical runs 44% of the time on Gemini, 43% on Perplexity, 35% on ChatGPT and 28% on Claude, as detailed in our enterprise AI monitoring study. A single daily check on a traditional rank tracker cannot measure a recommendation that flips four times out of ten.

According to Semrush, 62% of AI citations never name the brand at all, which means you cannot track your visibility by searching for your name. And according to Ahrefs, AI visibility correlates most with third-party mentions and video over on-page work, so an outage on your single scraping provider blinds your team to the review sites and forum threads steering the model.

Using our ChatGPT Scraper API, Google AI Mode API or Perplexity API lets you pull those real browser answers directly as JSON, and our AI Mentions API and MCP Server feed the classified brand and citation data straight into your engineering workflow.

How to Build a Multi-Source Data Architecture This Week

Protecting your product or marketing pipeline from the next scraping lawsuit takes an afternoon of engineering work, and it lowers your monthly bill at the same time. Instead of signing a single high-tier subscription, put a lightweight router in front of two independent APIs.

First, normalize your internal data schema around the fields your application actually consumes: the query or prompt, the organic ranking URLs, the AI answer text, the cited sources and the brands mentioned. Keeping vendor-specific JSON out of your core database means swapping an upstream provider takes a single configuration change.

Second, keep active API keys with two providers that do not penalize you for idle months. Because Honeyb's prepaid credits never expire and failed captures are never charged (Honeyb), you can run Honeyb as your primary feed for Google rank checks ($1.00 per 1,000) and enriched AI answers ($2.05 per 1,000 on ChatGPT, AI Overviews and AI Mode) while keeping a secondary key on a pay-as-you-go service, or keep Honeyb as your instant failover if you are currently locked into a legacy contract.

You can check every live line, verify the per-1,000 rates across all twelve engines and request your key in a minute on the Honeyb API hub.

Sources cited in this report

blog.googlesearchengineland.comsearchenginejournal.comseroundtable.combillhartzer.com2

Frequently asked questions

What is the Google vs. SerpApi lawsuit actually about?

Google sued SerpApi alleging that the company circumvented security measures protecting others' copyrighted content that appears in Google search results, and later amended its complaint to focus on content licensing terms. It tests whether copyright law can stop the automated collection of public search results, a question courts are still answering.

Who is winning the SerpApi lawsuit right now?

SerpApi has won the early procedural rounds in court. After the judge dismissed key DMCA claims from Google's initial complaint, Google filed an amended complaint focusing on licensed content, which the court also dismissed for a second time. While the case is not permanently over, Google's legal theories have failed twice to survive motions to dismiss.

What are the risks for my business if I rely on one SERP scraper?

Your main operational risk is sudden data blindness rather than direct courtroom liability. When a search engine targets a scraping vendor with litigation, it also deploys technical countermeasures that block proxies, alter HTML layouts or poison automated results. If your application relies on a single API key, those blocks halt your reporting until the vendor adapts.

Does paying for a legal shield protect my data uptime?

No. A legal shield like SerpApi's U.S. Legal Shield (included on plans from $150 a month) or SearchApi's Legal Protection Guarantee (from $100 a month) offers financial indemnification against legal claims in U.S. courts, but it does not keep the JSON flowing when an upstream DOM change or IP block breaks the scraper.

How do I keep my SERP and AI search data stable without doubling my budget?

Use two providers that bill on non-expiring prepaid credits or pay-as-you-go usage rather than fixed monthly subscriptions. Routing primary requests through a $1.00 per 1,000 provider where failed captures are free and keeping a secondary key on standby gives you automatic failover for a fraction of a $150 monthly plan.

Matiss Katanenko

About the author

Matiss Katanenko

Co-founder, Honeyb

My name is Matiss Katanenko and I co-founded Honeyb, the agent that gets brands recommended by AI, tracking how ChatGPT, Gemini, Claude, Perplexity and four more AI engines talk about them. Before Honeyb I ran SEO for fast-growing companies across the US and Europe, including one of America's 500 fastest-growing companies. The numbers I am proudest of: taking a site from zero to 200,000 monthly visitors in five months, and over $10M in client revenue attributed to organic search. I still run experiments across ten-plus of my own domains to test what actually works in SEO, programmatic SEO and AI search, and those experiments are what this blog reports on. My focus today is AI search visibility: how brands get retrieved, ranked and referenced by LLMs. I'm based in Riga, Latvia. In my free time I'm in the sauna, on a padel court, or behind a drum kit.

Prepaid credits, no subscription

Put AI search visibility in your product.

One key for eight AI engines. Every answer comes back classified: brand named, position, sentiment and cited pages, from $2.05 per 1,000 enriched answers.

ChatGPTClaudeGeminiPerplexity
See all API lines

We issue keys within one working day. Tell us your engines and volume.