This endpoint is not available for runs executed in live mode. It only works for runs executed in async or schedule mode. For live mode runs, results are returned directly in the API response.
Rate Limits
Run’s Routes Limits
To date, all /runs/xxx routes are subject to the same limit (e.g., 30 requests/minute for TRIAL plans). We are working to refine these quotas per endpoint (status, output, etc.) to better match usage patterns. Plans and limits will be updated in the documentation as soon as these changes take effect.
| Plan Tier | Max Requests/Second | Max Requests/Minute | Rationale |
|---|
| Trial | < 1 | 30 | Supports 2 concurrent runs @ 10s polling interval |
| Bronze | 1 | 60 | Supports 2 concurrent runs with more aggressive polling |
| Silver / Gold | 2.5 | 150 | Supports 5 concurrent runs @ 10s polling interval |
| Platinum / Diamond | 5 | 300 | Supports 10 concurrent runs @ 10s polling interval |
| Titanium | 10 | 600 | Supports 15 concurrent runs @ 10s polling interval |
Rate limits for polling run results via /v1/runs/{run_uid}/outputs. These limits support realistic polling patterns for customers who prefer polling over callbacks.
These limits are aligned with concurrent execution limits. For example, with a Silver/Gold plan (5 concurrent runs), you can poll all active runs every 10 seconds with comfortable headroom.
Capacity Examples
| Plan Tier | Polling Capacity | Use Case |
|---|
| Trial | Poll 2 runs every 10s | Basic polling during development |
| Bronze | Poll 2 runs every 10s with headroom | Small-scale polling |
| Silver / Gold | Poll 5 runs every 10s, or 1 run every 4s | Team polling operations |
| Platinum / Diamond | Poll 10 runs every 10s | Multi-workspace polling |
| Titanium | Poll 15 runs every 10s | Enterprise-scale polling |
Implementation Details:
- Rate limit type: Per-workspace, per-minute
- Error response: Standard 429 with
X-RateLimit-Type: /v1/runs/outputs
- Headers include
X-RateLimit-Remaining for visibility
Required range: 1 <= x <= 500