Thunder Compute · Rate Limits

Thundercompute Rate Limits

Thunder Compute does not publish explicit numeric request-per-minute rate limits for its REST API. The primary constraints are account-level resource quotas - the number and type of GPU instances an account may provision concurrently - which are governed by available GPU capacity, the account's tier/standing, and payment status rather than by API call throttling. New accounts may have lower concurrent-instance and GPU-type quotas that are raised on request. Specific numeric limits are not reconciled in this artifact.

Thundercompute Rate Limits is the machine-readable rate-limit profile for Thunder Compute on the APIs.io network, in the API Commons Rate Limits shape.

It captures 3 rate-limit definitions, measuring instances, gpus, and requests.

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

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

Tagged areas include GPU, Cloud, Infrastructure, AI, and Compute.

3 Limits Exhausted: HTTP 429
Method: generated, dated 2026-06-21.
Written by API Evangelist on 2026-06-21 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
GPUCloudInfrastructureAIComputeRate LimitingQuotasThrottling

Limits

Concurrent Instances account
instances
see provider console
Number of simultaneously running GPU instances; governed by quota and available capacity.
GPU Type Availability account
gpus
see provider console
Access to specific GPU models (e.g. H100, A100) may be gated by account tier and inventory.
API Requests account
requests
not published
No documented per-minute REST request cap; clients should still handle 429 with backoff.

Policies

Quota-Based Limits
Constraints are primarily concurrent-instance and GPU-type quotas, raised on request as accounts establish history and spend.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After if a 429 is returned.

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/thundercompute-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 form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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