Selenium Rate Limits
Selenium publishes no rate limits, and cannot: there is no vendor-operated endpoint to throttle. The W3C WebDriver protocol defines no rate limiting, no quota and no 429 status, and a Selenium Grid runs on hardware the consumer owns. What exists instead is CAPACITY, configured by the operator — a fixed pool of session slots plus a queue with a timeout. Those are recorded below as concurrency controls, deliberately NOT as rate limits, because they are the operator's settings rather than the provider's policy.
Selenium Rate Limits is the machine-readable rate-limit profile for Selenium on the APIs.io network, conforming to the API Commons Rate Limits specification.
Tagged areas include Automation, Browsers, End-to-End Testing, Quality Assurance, and Testing.
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.