Serper Rate Limits
Serper enforces two independent limits: a queries-per-second concurrency ceiling tied to the credit package you bought, and a credit balance that stops accepting queries at zero. Credits are deducted only for successful responses. Crucially, a query is not always one credit — the cost varies by search type, by result count, and by whether you use mini-batch. Serper publishes NO rate-limit response headers, so an agent cannot read its remaining budget or a retry delay from the wire.
Serper Rate Limits is the machine-readable rate-limit profile for Serper on the APIs.io network, in the API Commons Rate Limits shape.
It captures 4 rate-limit definitions.
Limit state is signalled in the published, request_headers, response_headers, and retry_after response headers.
Tagged areas include Search, SERP, Google Search, Artificial Intelligence, and LLM.
publishedrequest_headersresponse_headersretry_after
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.