Browser Use Rate Limits
Browser Use does not throttle on requests per second. The governing limit is CONCURRENT ACTIVE SESSIONS per project, set by plan, and the v3 billing account object returns it live as concurrentSessionLimit (with rateLimit kept as a legacy alias for the same number). Two 429 conditions are declared in the v4 contract. No RateLimit-* or Retry-After response headers were observed or documented — the SDKs retry 429 with exponential backoff on the client side instead.
Browser Use Rate Limits is the machine-readable rate-limit profile for Browser Use on the APIs.io network, in the API Commons Rate Limits shape.
It captures 7 rate-limit definitions, across the free, pay-as-you-go, dev, business, and scaleup tiers, measuring concurrent_active_sessions, agent_tasks, and session_timeout.
Limit state is signalled in the limit, remaining, reset, and retryAfter response headers, and an exhausted limit returns HTTP 429.
The profile also includes response codes documented for throttled, quotaExceeded, and note.
Tagged areas include AI Automation, Browser Automation, Rate Limiting, and Concurrency.
limitremainingresetretryAfter
Limits
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.