Armosec Rate Limits
ARMO does not publish fixed numeric rate limits for the ARMO Platform API. Access is gated by an account access key (X-API-KEY), and practical throughput is bounded by the size of your subscription (vCPU-based) and the scanning cadence of your connected clusters, registries, and repositories rather than by a documented per-minute request cap. Callers should implement retry with exponential backoff and honor 429 responses if throttled.
Armosec Rate Limits is the machine-readable rate-limit profile for ARMO on the APIs.io network, in the API Commons Rate Limits shape.
It captures 3 rate-limit definitions, measuring requests, keys, and scans.
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 Kubernetes Security, Cloud Native Security, Rate Limiting, and Quotas.
generated, dated 2026-07-11.
Limits
Policies
Sources
- https://hub.armosec.io/docs/armo-swagger-api
- https://api.armosec.io/openapi/v2/swaggerui
- https://hub.armosec.io/reference
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.