Runloop · Rate Limits

Runloop Rate Limits

Runloop does not publish numeric API request-per-minute limits in its docs or OpenAPI spec; the primary account-level constraints are resource-count caps (concurrent running devboxes and stored blueprints, snapshots and objects), which are lowest on the free trial and raised on paid and Enterprise plans. Documented trial caps are 3 running devboxes, 5 blueprints, 10 snapshots and 3 objects. Callers should still expect 429 throttling on abusive traffic and back off accordingly.

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

It captures 5 rate-limit definitions, measuring requests, devboxes, blueprints, snapshots, and objects.

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

Tagged areas include AI, Developer Environments, Devboxes, Coding Agents, and Rate Limiting.

5 Limits Throttle: 429
AIDeveloper EnvironmentsDevboxesCoding AgentsRate LimitingQuotasThrottling

Limits

API Requests Per Minute account
requests
not publicly documented
No numeric per-minute throttle is published; expect 429 on abusive traffic.
Concurrent Running Devboxes account
devboxes
3 on free trial; higher on paid / Enterprise
Maximum number of simultaneously running devboxes; raised on paid and Enterprise plans.
Stored Blueprints account
blueprints
5 on free trial; higher on paid / Enterprise
Maximum number of stored blueprints on the free trial.
Stored Snapshots account
snapshots
10 on free trial; higher on paid / Enterprise
Maximum number of stored disk snapshots on the free trial.
Stored Objects account
objects
3 on free trial; higher on paid / Enterprise
Maximum number of stored objects on the free trial.

Policies

Tiered Limits
Resource-count caps raise as accounts move from free trial to Basic, Pro and Enterprise plans.
Backoff Strategy
Clients should implement exponential backoff with jitter on 429 responses and honor any Retry-After header.
Idempotency
Devbox and run creation should be treated carefully on retry to avoid launching duplicate billable compute.

Sources