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, conforming to the API Commons Rate Limits specification.

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

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 Throttle: 429
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