SERPens vs HasData
Twelve verticals, camelCase body.
Response fields
| Field | SERPens | HasData |
|---|---|---|
| Organic results | Yes | Not documented |
| AI Overview | Yes | No |
| Knowledge panel | Yes | Yes |
| People Also Ask | Yes | No |
| Related searches | Yes | Yes |
| Sitelinks | Yes | Yes |
| Result source field | Yes | No |
| Pagination flags | Yes | Yes |
On our side, sitelinks, knowledge panel, People Also Ask and related searches arrive with the AI Overview endpoint, not with the plain organic call — one request returns all four alongside the overview and the results.
Compared against docs.hasdata.com, checked 2026-08-26. Blank cells mean the vendor did not document the field, not that it is missing.
Price
| Provider | Per 1,000 | Notes |
|---|---|---|
| SERPens | $1.16 | 100 free calls a month, no card |
| HasData | — | not published in our measurement |
Prices move. Both figures carry the date they were checked, and neither is a quote.
Surface
| Provider | Documented verticals | Response style |
|---|---|---|
| SERPens | 2 | camelCase |
| HasData | 12 | camelCase |
We cover two surfaces: web search, and web search with the AI Overview. That is fewer than most providers here, and it is a choice rather than a roadmap gap — one surface measured continuously and published in public is worth more than twenty nobody checks.
When HasData is the better choice
HasData returns a camelCase body with sitelinks and a knowledge panel, and covers twelve verticals. People Also Ask was not documented in our measurement.
What you get here that you do not there
A dedicated AI Overview endpoint returning Google's answer and the sources it credits, which HasData does not document. And a public measurement record: 4,185 queries run weekly through the same endpoint, with 50.8% carrying an overview as of 2026-W36.
Nobody else in this table publishes what their API returns. Ours is written out in full.
curl --request GET \
--url 'https://serpens.p.rapidapi.com/api/v1/search_ai_overview?q=best%20search%20apis&gl=us&hl=en&format=json' \
--header 'x-rapidapi-host: serpens.p.rapidapi.com' \
--header 'x-rapidapi-key: YOUR_KEY'Try it against your current provider
Free tier, no card. Point a staging build at the new base URL and diff the bodies.