Pangea · Rate Limits

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.

5 Limits Throttle: 429
SecurityAI SecurityAuthenticationAudit LogData ProtectionRate LimitingQuotasThrottling

Limits

Per-Service Request Limit project
requests
see provider documentation
Applied per service token and per service host; varies by plan.
Audit Bulk Log Items request
events
1000
Maximum events per /v2/log and /v2/log_async request.
IP Intel Bulk Items request
ips
100
Maximum IP addresses per /v2/reputation, /v2/geolocate, and related calls.
AI Guard Text Size request
bytes
20480
Plain-text input to /v1/text/guard is limited to roughly 20 KiB.
Intel Provider Limit project
requests
see provider documentation
Intel and File Scan throughput depends on the configured upstream provider.

Policies

Free-Tier Balance
Usage is gated by the complimentary monthly balance before pay-as-you-go billing and any applicable throttling.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources