Brightdata Rate Limits
Bright Data enforces per-zone and per-account concurrency and request-rate limits rather than a single global quota. The managed scraping APIs (Web Unlocker, SERP, Web Scraper) and the Scraping Browser have concurrent-request / concurrent-session ceilings that scale with the account plan and can be raised on request. Proxy zones are constrained primarily by bandwidth and concurrency. Specific numeric limits are configured per zone in the control panel and are not reconciled in this artifact.
Brightdata Rate Limits is the machine-readable rate-limit profile for Bright Data on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 4 rate-limit definitions, measuring concurrent_requests, concurrent_sessions, concurrent_connections, and bandwidth.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Web Data, Web Scraping, Proxy, Rate Limiting, and Quotas.
Limits
Policies
Sources
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for rate limits
4 MCP tools reach this
find_rate_limitsBrowse and filter every rate limit in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/brightdata-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.