specification: API Commons Rate Limits
specificationVersion: '0.1'
schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/RateLimits
provider: Aqua Security
providerId: aqua-security
created: '2026-05-04'
# Provenance stamped 2026-08-11: this artifact was written by the API Evangelist
# bulk sweep dated 2026-05-04, not harvested from the provider. See roadmap#35.
method: generated
modified: '2026-05-05'
reconciled: false
tags:
- Cloud Native
- Containers
- Kubernetes
- Runtime Protection
- Security
- Vulnerability Scanning
- Rate Limiting
- Quotas
- Throttling
description: Aqua Security does not publish concrete rate-limit numbers, throttling thresholds, or response-header
  conventions. This artifact records the gap; see notes for research findings.
notes: Aqua Security's API documentation requires authentication. Public rate-limit numbers, throttling
  thresholds, and response-header conventions are not published.
sources:
- https://www.aquasec.com
- https://docs.aquasec.com
- https://www.aquasec.com/pricing/
responseCodes:
  throttled: 429
limits:
- name: Per-contract limits
  scope: account
  metric: varies
  limit: see provider integration agreement
  notes: No public rate-limit numbers; throughput is governed by individual customer or partner contracts.
policies:
- name: Backoff Strategy
  description: Clients should implement exponential backoff with jitter and honor any Retry-After header
    that may be returned, even though the provider does not publish formal retry semantics.
- name: Contract-Scoped Limits
  description: Quotas, burst, and concurrency ceilings are governed by the individual customer or partner
    contract rather than a public policy. Coordinate with the provider to confirm thresholds before scaling
    traffic.
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com