Nitric · Rate Limits

Nitric Rate Limits

Nitric is a framework / IaC SDK and CLI, not a hosted API, so Nitric itself imposes no API rate limits or quotas. Any throttling experienced by an application built with Nitric comes from the underlying cloud services that the chosen provider plugin provisions - for example AWS API Gateway request quotas, SQS throughput limits, DynamoDB capacity, or cloud-account service quotas on AWS, Google Cloud, or Azure. Specific limits depend entirely on the target cloud and the resources declared, and are not reconciled in this artifact.

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

It captures 2 rate-limit definitions, measuring 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 Infrastructure from Code, Cloud Framework, SDK, CLI, and Rate Limiting.

2 Limits Exhausted: HTTP 429
Method: generated, dated 2026-06-20.
Written by API Evangelist on 2026-06-20 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
Infrastructure from CodeCloud FrameworkSDKCLIRate LimitingQuotas

Limits

Framework Rate Limits framework
requests
not applicable
Nitric is an SDK/CLI; it does not meter or throttle API calls itself.
Cloud Provider Service Quotas account
requests
see target cloud documentation
Throttling derives from the provisioned cloud services (e.g. AWS API Gateway, SQS, SNS, DynamoDB) and the cloud account's service quotas.

Policies

Cloud-Native Quotas
Effective limits are defined by the target cloud provider's service quotas for the resources Nitric provisions, not by Nitric.
Backoff Strategy
Applications should implement exponential backoff with jitter and honor Retry-After when calling provisioned cloud services that return 429.

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