Pangea Rate Limits
Pangea enforces per-project, per-service request limits across its security service APIs. Limits are applied per service token and per service host (for example audit.aws.us.pangea.cloud), and are governed by the project's billing tier and configured providers. Bulk endpoints (Secure Audit Log /v2/log, IP Intel /v2/reputation) cap items per request - up to 1000 audit events and up to 100 IPs per call. Specific per-service request-per-second values are not published and are not reconciled in this artifact.
Pangea Rate Limits is the machine-readable rate-limit profile for Pangea on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 5 rate-limit definitions, measuring requests, events, ips, and bytes.
The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Security, AI Security, Authentication, Audit Log, and Data Protection.
Limits
Policies
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/pangea-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.