SERPens vs ScaleSERP
Eleven verticals, volume pricing.
Response fields
| Field | SERPens | ScaleSERP |
|---|---|---|
| Organic results | Yes | Yes |
| AI Overview | Yes | No |
| Knowledge panel | Yes | Not documented |
| People Also Ask | Yes | Not documented |
| Related searches | Yes | Not documented |
| Sitelinks | Yes | Not documented |
| Result source field | Yes | No |
| Pagination flags | Yes | Not documented |
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 trajectdata.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 |
| ScaleSERP | $6.60 | $66 for 10,000; falls to $2.40 per 1,000 at 250,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 |
| ScaleSERP | 11 | not documented |
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 ScaleSERP is the better choice
ScaleSERP publishes a clear volume ladder and a small free allowance. Its response fields were not documented in enough detail for us to compare block by block, so the table below leaves those cells blank rather than guessing.
What you get here that you do not there
A dedicated AI Overview endpoint returning Google's answer and the sources it credits, which ScaleSERP 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.