Picus Security Rate Limits
The Picus Customer API applies tiered, per-endpoint rate limits on a per-minute basis, enforced by client IP. Read-oriented endpoints get higher limits than write-oriented endpoints. Picus does not publish a full per-endpoint limit table; instead every response carries the limit for the endpoint that was called in the X-Ratelimit-* headers, and the docs give two worked examples.
Picus Security Rate Limits is the machine-readable rate-limit profile for Picus Security 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 limit, remaining, reset, and reset_format response headers, and an exhausted limit returns HTTP 429.
The profile also includes response codes documented for throttled and throttled_description.
Tagged areas include Rate Limiting and Security Validation.
limitremainingresetreset_format
Limits
Sources
- https://apidocs.picussecurity.com/docs/rate-limit
- https://apidocs.picussecurity.com/docs/response-codes-errors
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.