Blaxel · Rate Limits

Blaxel Rate Limits

Blaxel constrains usage primarily through spend-tier concurrency limits rather than fixed per-second request quotas. Each account sits in a tier (Tier 0-9) that caps the number of concurrent sandboxes - roughly 10 on the free Tier 0, 50 at Tier 1, 200 at Tier 2, and scaling to 100,000+ at Tier 9. Additional operational limits apply to hosted workloads: synchronous agent invocations run up to about 100 seconds, asynchronous invocations up to about 10 minutes, and batch jobs up to about 24 hours. Control plane REST endpoints may also be throttled to protect the platform. Specific per-endpoint request rates are not reconciled in this artifact.

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

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

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

Tagged areas include AI, Agents, Infrastructure, Sandboxes, and MCP.

6 Limits Throttle: 429
AIAgentsInfrastructureSandboxesMCPComputeRate LimitingQuotasThrottling

Limits

Concurrent Sandboxes account
sandboxes
tier-based (10 on Tier 0 up to 100,000+ on Tier 9)
Primary concurrency limit; raises automatically as the account moves up spend tiers.
Synchronous Agent Invocation Duration deployment
seconds
~100 seconds
Maximum wall-clock duration for a synchronous agent HTTP request.
Asynchronous Agent Invocation Duration deployment
seconds
~600 seconds
Maximum duration for an asynchronous agent invocation.
Batch Job Duration job
seconds
~86400 seconds (24 hours)
Maximum runtime for a batch job execution.
Sandbox Idle TTL sandbox
seconds
configurable (e.g. ~600 seconds default idle TTL)
Idle sandboxes are stopped after their TTL to conserve compute.
Control Plane Requests account
requests
see provider documentation
REST control plane endpoints may be throttled; honor 429 and Retry-After.

Policies

Tiered Concurrency
Concurrency ceilings raise as accounts add credits and move through Tier 0-9.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.
Idle Reclamation
Idle sandboxes and hosted workloads scale to zero / stop after their TTL to limit spend.

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