SerpApi alternative: how Fenlight compares
Fenlight is a Google results and AI-visibility API from Waggle. SerpApi is a search API that covers far more engines and result types than Fenlight does. This page sets out what each does, what each costs and what each limits, and says plainly where SerpApi is the stronger fit.
The short version
- Choose SerpApi if you need engines other than Google, Google products such as Maps, Shopping, News or Scholar as separate APIs, hourly throughput guaranteed by plan, an uptime SLA, or security attestations such as SOC 2 Type II.
- Consider Fenlight if your work is Google results plus AI visibility: what ChatGPT and Claude say about your brand, the Reddit and Quora threads Google ranks for a category, keyword ideas in Arabic, or MCP access.
- On published prices a Fenlight live results page and a SerpApi search overlap: $2.00 to $3.80 per 1,000 live pages, against $1.96 to $25.00 per 1,000 searches. The two are not counted the same way, so read the notes under the prices.
Side by side
| Fenlight | SerpApi | |
|---|---|---|
| Engines and APIs | Google is in production. DuckDuckGo is in beta; Bing, Brave and Yahoo are experimental and often blocked. | Google plus Bing, DuckDuckGo, Yahoo, Baidu, Naver, Yandex, YouTube, Amazon, Walmart, eBay and more: its pricing page lists 121 APIs (SerpApi pricing). |
| Google result types | Organic results, People Also Ask, related searches and the knowledge panel on a results page; the local pack and shopping as priced add-ons. | A Google Search API, plus separate APIs for Maps, Shopping, News, Images, Videos, Scholar, Trends, Autocomplete and more. |
| Google's AI features | Fenlight does not measure Google's AI Overview, and it has no AI Mode. | SerpApi lists a Google AI Mode API and a Google AI Overview API. |
| AI assistants | ChatGPT, Claude and Gemini through POST /v1/ai/answers: mention rate with a 95% interval, citations and cited domains. Not yet available: Perplexity. | Lists APIs for Bing Copilot, Brave AI Mode, Duck AI and Naver AI Mode. Check its documentation for what each returns. |
| Price | Credits from a Vera plan, $19 to $399 a month. A live results page is 7 credits and a cached page 1: about $2.00 to $3.80 per 1,000 live pages. Each page after the first of a deeper search is 14 credits. | Monthly plans by number of searches, from $25 for 1,000 to $106,050 for 54,000,000. Month-to-month, cancel any time. |
| Free tier | 3,000 free credits for a new Vera account, granted once, usable at up to 1,500 a day: 428 live pages. | A Free plan: 250 searches a month, with 50 successful searches an hour guaranteed. |
| What is charged | What was served. A failed request costs nothing. A repeat of the same search by your key is served from a cache that is private to the key, up to 24 hours old by default, for 1 credit instead of 7; fresh: true searches live. | Only successful searches count: cached, errored and failed searches do not. Its cache expires after 1 hour; no_cache forces a fresh fetch. |
| Rate limits | 60 requests a minute and at most 5 at once, per key. | Guaranteed throughput by plan, from 50 searches an hour (Free) to 20,000 (Searcher) and more on larger plans. |
| Authentication | Authorization: Bearer or X-API-Key header. | An api_key parameter (the only method its Google Search API page documents). |
| Assurances | No uptime SLA, security certification or legal-indemnity programme is published. | Uptime SLAs of up to 99.97%, SOC 2 Type II, SOC 3 and ISO 27001 certification, and a U.S. Legal Shield of up to $2 million on its larger plans. |
| Arabic and the Gulf | 115 shortcut cities (24 nameable in Arabic), 139,425 Google locations, Arabic keyword ideas. | A location parameter at city level, with gl and hl, and a locations API for exact names. |
| MCP and client libraries | A remote MCP server with 8 tools. A plain HTTP API, with examples in Python, TypeScript and curl. | Lists integrations for Ruby, Python, JavaScript, Go, PHP, Java, Rust, .NET, Swift, C++, a CLI and MCP. |
Price per 1,000 Google results
Fenlight's credits come from a Vera plan (Vera pricing), at about $0.00029 to $0.00054 a credit, so a live results page (7 credits) costs the amounts below if you use the plan's credits.
| Vera plan | Price | Credits a month | Live pages a month | Per 1,000 live pages |
|---|---|---|---|---|
| Forager | $19 a month | 35,000 | 5,000 | $3.80 |
| Builder | $59 a month | 150,000 | 21,428 | $2.75 |
| Scale | $149 a month | 500,000 | 71,428 | $2.09 |
| Studio | $399 a month | 1,400,000 | 200,000 | $2.00 |
SerpApi's plans, from SerpApi pricing:
| SerpApi plan | Price | Searches a month | Searches an hour guaranteed | Per 1,000 searches |
|---|---|---|---|---|
| Free | $0 a month | 250 | 50 | free |
| Starter | $25 a month | 1,000 | 200 | $25.00 |
| Developer | $75 a month | 5,000 | 1,000 | $15.00 |
| Production | $150 a month | 15,000 | 3,000 | $10.00 |
| Big Data | $275 a month | 30,000 | 6,000 | $9.17 |
| Searcher | $725 a month | 100,000 | 20,000 | $7.25 |
| Volume | $1,475 a month | 250,000 | 50,000 | $5.90 |
| Infrastructure | $2,750 a month | 500,000 | 100,000 | $5.50 |
| Cloud 1M to Cloud 54M | $3,750 to $106,050 a month | 1,000,000 to 54,000,000 | 110,000 to 640,000 | $3.75 to $1.96 |
SerpApi's lowest published price per 1,000 searches is $1.96 (Cloud 54M).
- Use matters. Both prices are monthly plans. The figures above assume you use all of a plan's allowance; Vera says unused credits roll over while your account is open.
- Counting differs. SerpApi's FAQ says the number of results in a response does not change what a search counts as. Fenlight charges a page per ten results: the first is 7 credits and each page after it 14, so depth 30 is three pages, 35 credits live. The local pack (+14 credits) and shopping (+7) are charged once per request, only if they return something.
- Repeats. SerpApi does not count cached searches, and its cache lasts 1 hour. Fenlight serves a repeat from your key's cache for 1 credit, for up to 24 hours by default, so send
fresh: truewhen you need a live result. - Failures. Neither charges for a failed request.
Where SerpApi is stronger
- Coverage. 121 APIs, across Google, Bing, DuckDuckGo, Yahoo, Baidu, Naver, Yandex, YouTube, Amazon, Walmart, eBay and others. Fenlight is a Google product, with other engines in beta or experimental.
- Google beyond the results page. SerpApi has separate APIs for Maps, Shopping, News, Images, Videos, Scholar and Trends, and for Google's AI Mode and AI Overview. Fenlight's local pack and shopping are add-ons to a results-page search.
- Published service levels. Guaranteed searches an hour on every plan, an uptime SLA of up to 99.97%, SOC 2 Type II, SOC 3 and ISO 27001, a U.S. Legal Shield and a ZeroTrace mode on its larger plans. Fenlight publishes none of these.
- Throughput. Guaranteed throughput from 200 to 640,000 searches an hour, by plan. Fenlight allows 60 requests a minute and at most 5 at once, per key.
- Client libraries. Integrations for a dozen languages and tools. Fenlight is an HTTP API with examples in Python, TypeScript and curl.
- A recurring free plan. 250 searches every month. Fenlight's free credits are granted once.
Where Fenlight fits
- AI answers. Ask ChatGPT and Claude a buyer's question, repeat it, and get a mention rate with a 95% interval, competitors, citations and cited domains.
- The radar. List the Reddit and Quora threads Google ranks for a category, with the list articles and videos beside them.
- Arabic and the Gulf. Keyword ideas from an Arabic seed, and Gulf cities by their Arabic names, among 139,425 Google locations.
- MCP. A remote server with 8 tools at
https://fenlight.waggle.ae/mcp, listed in the official MCP registry asae.waggle/fenlight. - One key for Fenlight and Vera. The same Vera key and credit balance work on both.
What Fenlight does not do
- It is not a drop-in for SerpApi: the request and the response differ (see below).
- Google is the only engine in production. DuckDuckGo is in beta; Bing, Brave and Yahoo are experimental and often blocked.
- Fenlight does not measure Google's AI Overview (its AI Overview field says unmeasured) and has no AI Mode.
- Its
devicesetting does not change the results, so mobile and desktop results cannot be compared. - It has no result offset: you ask for
depthresults from the top, to 100. - Not yet available in AI answers: Perplexity.
- It allows 60 requests a minute and at most 5 at once, per key.
Moving from SerpApi
This is a rewrite of the request and of the code that reads the answer, not a change of base URL. A SerpApi call, from its documentation (SerpApi Google Search API documentation):
curl -G https://serpapi.com/search \ --data-urlencode "engine=google" \ --data-urlencode "q=coffee" \ --data-urlencode "location=Austin, Texas, United States" \ --data-urlencode "gl=us" \ --data-urlencode "hl=en" \ --data-urlencode "api_key=$SERPAPI_API_KEY"
The same search on Fenlight, with your Vera key in FENLIGHT_API_KEY:
curl -X POST https://fenlight.waggle.ae/v1/serp/google \
-H "Authorization: Bearer $FENLIGHT_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"q": "coffee",
"location": "Austin, Texas, United States",
"gl": "us",
"hl": "en",
"depth": 10
}'
That is 7 credits for a live page. How the fields map:
| SerpApi | Fenlight |
|---|---|
GET https://serpapi.com/search | POST https://fenlight.waggle.ae/v1/serp/google with a JSON body |
api_key parameter | Authorization: Bearer or X-API-Key header |
engine=google | The path: /v1/serp/google |
q, gl, hl | The same names |
location | location: a place name, such as Austin, Texas, United States, or a Google location_code |
device | device is accepted but does not change the results |
start (offset) | No offset: depth (1 to 100) asks for results from the top |
no_cache=true | "fresh": true |
organic_results | organic |
related_questions | serp_features.people_also_ask |
related_searches | serp_features.related_searches |
knowledge_graph | serp_features.knowledge_graph |
local_results | serp_features.local_pack, when features includes local_pack (+14 credits) |
shopping_results | serp_features.shopping, when features includes shopping (+7 credits) |
Run the same few keywords through both for a week and compare the organic lists before you switch anything.
Sources
Every fact about another company on this page was read from its own pages, checked 19 October 2026. Prices and features change, so check the source before you decide.
- SerpApi pricing: plans, prices, searches and throughput per plan, how searches are counted, the list of APIs, the SLA, certifications and integrations.
- SerpApi Google Search API documentation: the endpoint, the parameters, authentication, the cache and the response sections.
- Vera pricing: Vera's plans, the free credits and what happens to unused credits.