Nimbleway · Rate Limits

Nimbleway Rate Limits

Nimble SDK enforces a per-API-key rate limit. The default ceiling is 83 QPS (5,000 QPM) applied across driver types (vx6, vx8, vx10). Higher limits are available via sales. Rate-limit state is signalled on every response via X-RateLimit-* headers; exceeding the limit returns HTTP 429 with retry_after.

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

It captures 2 rate-limit definitions, measuring requests_per_second and requests_per_minute.

Limit state is signalled in the limit, remaining, and reset response headers, and an exhausted limit returns HTTP 429.

The profile also includes response codes documented for throttled.

Tagged areas include Rate Limiting and Web Data.

2 Limits Exhausted: HTTP 429 limitremainingreset
Transcribed from the provider's documentation on 2026-07-20 — docs.nimbleway.com/api-reference/introduction.
View Source
Rate LimitingWeb Data

Limits

Default per-key request rate (per second) api_key
requests_per_second · second
83
Default per-key request rate (per minute) api_key
requests_per_minute · minute
5000

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