Netdata Rate Limits
Netdata does not publicly document specific rate limits for either the Agent API or the Cloud API as of June 2026. The Agent API runs on individual nodes and inherits resource limits from the local system. The Cloud API uses Bearer token authentication with no stated per-token rate limits in public documentation. Standard HTTP 429 responses are used if throttling occurs.
Netdata Rate Limits is the machine-readable rate-limit profile for Netdata on the APIs.io network, in the API Commons Rate Limits shape.
It captures 2 rate-limit definitions, measuring requests_per_minute.
Limit state is signalled in the retryAfter response header, and 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 response codes documented for throttled.
Tagged areas include Rate Limiting, Monitoring, and Observability.
retryAfter
generated, dated 2026-06-12.
Limits
Sources
- https://learn.netdata.cloud/docs/netdata-cloud/authentication-&-authorization/api-tokens
- https://learn.netdata.cloud/docs/rest-api/api
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.