Runway · Rate Limits

Runwayml Rate Limits

Runway governs the developer API through per-organization usage tiers rather than a single published global rate limit. Tiers set how many generation tasks you can have running concurrently (per model) and your request throughput; organizations move up tiers with spend / usage history, and higher limits are available by exception for enterprise customers. Because generation is asynchronous, the practical constraint is task concurrency and your credit balance, not a per-minute request cap. Clients polling GET /tasks/{id} should not poll more than once every five seconds per task.

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

It captures 4 rate-limit definitions, measuring concurrent_tasks, requests, and credits.

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

Tagged areas include Video Generation, AI Video, Generative AI, Rate Limiting, and Quotas.

4 Limits Throttle: 429
Video GenerationAI VideoGenerative AIRate LimitingQuotas

Limits

Task Concurrency organization
concurrent_tasks
per usage tier (per model)
The main constraint - how many generation tasks can run at once, set by your org's usage tier and model.
Request Rate organization
requests
per usage tier
Request throughput is governed by tier; no single fixed global per-minute number is published.
Task Polling task
requests
<= 1 poll / 5 seconds per task
Runway advises not expecting task updates more often than once every five seconds for a given task.
Credit Balance organization
credits
prepaid balance
Tasks are billed in credits; an empty balance blocks new billable generation tasks.

Policies

Usage Tiers
Concurrency and rate limits scale by organization usage tier; higher limits available by exception for enterprise.
Backoff Strategy
On 429, back off with exponential delay and jitter and honor any Retry-After header before retrying.
Asynchronous Draining
Prefer increasing task concurrency headroom over aggressive polling; poll each task no more than once every five seconds.

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/runwayml-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.