The research endpoint has a separate rate limit that applies to both development and production keys for creating research tasks. Note that polling requests to retrieve the status of ongoing research tasks follow the default rate limits as decribed above.
When you exceed the rate limit, the API returns a 429 Too Many Requests response with a retry-after header indicating the number of seconds to wait before making another request.
HTTP/2 429 Too Many Requestsretry-after: 60{ "error": "Your request has been blocked due to excessive requests. Please reduce the rate of requests."}
We recommend implementing retry logic that respects the retry-after header value to automatically handle rate limiting in your application.
Access to production keys requires either an active Paid Plan or PAYGO enabled. More information can be found here.
When using the REST API, ensure you include your API key in the header to apply the correct rate limits.
