Product
Documentation
Two endpoints, six parameters, one response shape.
Headers
Authentication
Keys are issued and billed by RapidAPI. Every request carries two headers.
x-rapidapi-key: YOUR_KEY
x-rapidapi-host: serpens.p.rapidapi.com
Three
Endpoints
| Path | Returns |
|---|---|
GET /api/v1/search | Organic results and the blocks Google rendered |
GET /api/v1/search_ai_overview | The same, plus Google's AI Overview and its citations |
POST /mcp | Stateless JSON-RPC for MCP clients — two tools, no session to manage |
Contract
Handling the response
Optional blocks are absent when Google rendered nothing. Not null, not an empty array.
// correct
if ('aiOverview' in body) { … }
// wrong — throws on a normal response
if (body.aiOverview !== null) { … }This is the single most common integration bug, and it is worth getting right on day one: roughly half of all queries come back without an overview.
Reliability
Errors and retries
| Status | Meaning | What to do |
|---|---|---|
400 | A parameter failed validation | Fix the request. Retrying will not help, and it is billed |
429 | Rate limit | Back off exponentially. Do not retry immediately |
5xx | Upstream trouble | Retry with backoff, up to three attempts |
Latency runs about 1.1 seconds at the median and 2.8 at the 95th percentile. Set your client timeout above three seconds or you will cancel calls that were about to succeed — and be billed for them anyway.
Get a key
Key in under a minute, no card. Billing lives on RapidAPI, so the first call is a copy-paste away.