Skip to main content

​
Request Limits

The Octoparse MCP server allows up to 300 requests per minute per OAuth session. This limit applies to all MCP tool calls, including search, execution, export, and task management.

​
What happens when the limit is exceeded

If the request limit is exceeded, the server returns HTTP 429 Too Many Requests.
Use the response headers below to decide when to retry instead of relying on fixed wait times.

​
Retry headers

HeaderDescription
X-RateLimit-LimitMaximum number of requests allowed in the current rate limit window.
X-RateLimit-RemainingNumber of requests remaining in the current window.
X-RateLimit-ResetISO 8601 timestamp showing when the current window resets. Use this value to determine the next safe retry time.
X-RateLimit-WindowLength of the current rate limit window in milliseconds.
1

Check the status code

If the server returns 429, treat the request as rate-limited rather than failed permanently.
2

Read the retry headers

Check X-RateLimit-Remaining and X-RateLimit-Reset to understand whether the current window is exhausted and when it will reset.
3

Retry after reset

Wait until the time indicated by X-RateLimit-Reset before sending the next request.