Urlbox · Rate Limits

Urlbox Rate Limits

Urlbox enforces two layers of limits: a requests-per-minute (RPM) throttle that scales by subscription tier, and a monthly render quota tied to each plan's included render allowance. Requests served from cache do not count against the render quota. Render usage is exposed on every response via x-renders-used, x-renders-allowed, x-renders-remaining, and x-renders-reset headers, and exceeding the RPM throttle returns HTTP 429.

Urlbox Rate Limits is the machine-readable rate-limit profile for Urlbox on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 6 rate-limit definitions, measuring requests and renders.

The profile also includes 4 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Screenshots, Rendering, PDF, Video, and Web Capture.

6 Limits Throttle: 429
ScreenshotsRenderingPDFVideoWeb CaptureRate LimitingQuotasThrottling

Limits

Requests Per Minute (Lo-Fi) account
requests
30
Lo-Fi tier per-minute request throttle.
Requests Per Minute (Hi-Fi) account
requests
60
Hi-Fi tier per-minute request throttle.
Requests Per Minute (Ultra) account
requests
250
Ultra tier per-minute request throttle.
Requests Per Minute (Business) account
requests
1000
Business tier per-minute request throttle.
Requests Per Minute (Enterprise) account
requests
unlimited
Enterprise tier negotiated/unlimited per-minute throughput.
Monthly Render Quota account
renders
per plan allowance
Equal to the included render allowance of the active plan; over-quota usage triggers an automatic tier upgrade. Cached renders are not counted.

Policies

Cache Exemption
Requests served from the render cache do not count against the monthly render quota or RPM throttle.
Automatic Tier Upgrade
Sustained usage above the plan allowance automatically upgrades the account to the next tier.
Usage Headers
x-renders-used, x-renders-allowed, x-renders-remaining, and x-renders-reset headers report quota state on every response.
Backoff Strategy
Clients should implement exponential backoff with jitter on HTTP 429 responses.

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.
All 92 tools

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/urlbox-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.