Skip to main content
Rate limits and quotas are enforced per plan. Your plan determines how many requests you can make in a period, how large result pages can be, and which topics and languages you can access.

​
Rate limit headers

Authenticated responses include the current rate limit in headers:
  • X-RateLimit-Limit: the maximum requests allowed in the current window.
  • X-RateLimit-Remaining: how many requests remain in the window.
  • X-RateLimit-Reset: the unix timestamp when the window resets.
When a request is rejected, the API also sets an X-Deny-Reason header with the reason. 429 responses include a Retry-After header with the number of seconds to wait.

​
Quota exceeded

When you exceed your plan’s request quota, the API returns 402 Payment Required:

​
Rate limited

When you exceed your plan’s rate limit, the API returns 429 Too Many Requests:

​
Plan-dependent limits

Several behaviors depend on your plan’s entitlements:
  • Articles per page: the maximum number of articles returned per page. Your limit parameter is capped at this value.
  • Historical trends: how far back trending data is available. Requests for older dates return 402.
  • Allowed topics and languages: the topics and languages you can query. Unsupported values return 402.
  • Article content: full article content is only returned for plans that include it.
  • Article fields: fields like id and translations are only returned for plans that include them.
  • MCP access: the MCP server is only available for plans with MCP access. Each tools/call consumes one quota unit.

​
Best practices

  • Add retry logic with exponential backoff for 429 responses.
  • Cache responses where freshness allows.
  • Keep limit within your plan’s per-page allowance.
  • Contact support if you need a plan change.