Nscale · Rate Limits

Nscale Rate Limits

Nscale enforces per-account rate limits on serverless inference, typically expressed as requests per minute (RPM) and tokens per minute (TPM) per model, with limits scaling by account tier and usage. GPU compute is governed by organization-level capacity quotas rather than request-rate limits. Specific per-model values are not reconciled in this artifact.

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

It captures 4 rate-limit definitions, measuring requests, tokens, concurrency, and gpu_capacity.

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 AI, GPU, Inference, Serverless, and Cloud Compute.

4 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
AIGPUInferenceServerlessCloud ComputeRate LimitingQuotasThrottling

Limits

Requests Per Minute (RPM) account
requests
see provider documentation
Per-model RPM on serverless inference, varies by tier and model.
Tokens Per Minute (TPM) account
tokens
see provider documentation
Per-model TPM on serverless inference, varies by tier and model.
Concurrent Requests account
concurrency
see provider documentation
Maximum in-flight inference requests per account/key.
GPU Compute Quota organization
gpu_capacity
see provider documentation
Organization-level GPU/instance capacity quota for compute provisioning, not a request rate.

Policies

Tiered Limits
Limits raise as accounts move from free to paid usage and via Enterprise agreements.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

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