Steel Dev Rate Limits
Steel Cloud meters usage primarily by concurrent browser sessions and monthly browser hours rather than fixed requests-per-second limits, with bundled proxy bandwidth and CAPTCHA solve allotments per plan. Concurrency caps, monthly browser-hour allotments, proxy bandwidth, and CAPTCHA solves scale with the subscription tier (Hobby, Starter, Developers, Startups, Enterprise). Self-hosted steel-browser instances have no Steel-imposed limits beyond local hardware. Specific per-tier concurrency and request values are not reconciled in this artifact.
Steel Dev Rate Limits is the machine-readable rate-limit profile for Steel on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 5 rate-limit definitions, measuring sessions, browser_hours, gigabytes, solves, and requests.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Browser, Web Automation, Scraping, AI Agents, and Open Source.
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/steel-dev-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.