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, conforming to the API Commons Rate Limits specification.
It captures 3 rate-limit definitions, measuring requests, keys, and scans.
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.
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.
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/armosec-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.