Kubescape · Rate Limits

Kubescape Rate Limits

Neither the open-source Kubescape tool nor the hosted ARMO Platform Customer API publishes fixed numeric request-rate limits. For the open-source CLI and in-cluster Operator, scan throughput is bounded only by your own cluster and host resources. For the hosted ARMO Platform Customer API (https://api.armosec.io/api/v1), the effective ceiling is the plan's worker- node / data-retention allowance rather than a documented per-minute request cap; expect standard HTTP 429 throttling and Retry-After handling on the managed service.

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

It captures 4 rate-limit definitions, measuring requests, nodes, 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, Container Security, Rate Limiting, and Quotas.

4 Limits Exhausted: HTTP 429
Method: generated, dated 2026-07-11.
Written by API Evangelist on 2026-07-11 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
Kubernetes SecurityCloud Native SecurityContainer SecurityRate LimitingQuotas

Limits

Customer API Requests account
requests
not published
No fixed numeric request-rate limit is documented for the ARMO Platform Customer API.
Worker Node Allowance account
nodes
per plan
ARMO Platform meters the number of protected worker nodes per plan tier rather than API calls.
Self-Hosted Scan Throughput deployment
scans
hardware-bound
Open-source CLI/Operator scanning is constrained by your own cluster and host resources, not by a vendor limit.
In-Cluster Component API cluster
requests
cluster-bound
OpenAPI/Swagger-documented Operator component APIs run inside your cluster; throughput is bounded by your resources.

Policies

Backoff Strategy
Clients of the ARMO Platform Customer API should implement exponential backoff with jitter and honor Retry-After on 429 responses.
Scheduled Scanning
Operator and registry scans run on configurable cron schedules; tune frequency to control load rather than relying on a request cap.

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