API reference

Usage & quotas

Check consumption, understand how the monthly quota and rate limit apply, and what happens at the limit.

Check usage

GET/v1/usage

request

curl "https://serp-api.hoangha.shop/v1/usage" -H "X-API-Key: sk_..."

response

{
  "tier": "pro",
  "monthly_quota": 10000,
  "used_this_month": 1342,
  "remaining": 8658,
  "rate_limit_per_min": 120
}

Field	Type	Description
tier	string	The plan tier attached to the key.
monthly_quota	integer	Requests allowed per calendar month. 0 means unlimited (no monthly cap).
used_this_month	integer	Requests consumed so far this month.
remaining	integer \| null	Requests left this month, or null when the quota is unlimited.
rate_limit_per_min	integer	Maximum requests per minute for this key.

What counts against quota

Each accepted POST /v1/search that starts a crawl consumes one unit of the monthly quota.
A cached result (cached: true) does not consume quota.
A request rejected by a locale gate or the quota check itself is refunded / not counted.
Polling for results (GET /v1/search/{job_id}) and GET /v1/usage do not consume the monthly quota.

At the limit

When the monthly quota is exhausted, further searches return 429 with detail monthly quota exceeded. The quota resets at the start of the next calendar month. Sustained bursts above rate_limit_per_min are also throttled.

Design for caching

Because cached hits are free, avoid re-crawling the same keyword/location/device within the cache window. Batch distinct queries and let repeats ride the cache. See Guides.