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.
Limits
Policies
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/thundercompute-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.