SERPens vs Serper
The contract we are compatible with.
Response fields
| Field | SERPens | Serper |
|---|---|---|
| Organic results | Yes | Yes |
| AI Overview | Yes | No |
| Knowledge panel | Yes | Yes |
| People Also Ask | Yes | Yes |
| Related searches | Yes | Yes |
| Sitelinks | Yes | Yes |
| Result source field | Yes | No |
| Pagination flags | Yes | No |
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 serper.dev, 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 |
| Serper | $0.30 | volume tier; entry tier published at $1.00 per 1,000 |
Prices move. Both figures carry the date they were checked, and neither is a quote.
Surface
| Provider | Documented verticals | Response style |
|---|---|---|
| SERPens | 2 | camelCase |
| Serper | 13 | 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 Serper is the better choice
Serper is cheaper per call at volume and covers thirteen verticals to our two. We are compatible with it on purpose: if the web search endpoint is all you use, switching costs one line, and you gain the AI Overview endpoint. If you use the image, news or shopping verticals, stay where you are.
What you get here that you do not there
A dedicated AI Overview endpoint returning Google's answer and the sources it credits, which Serper 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.