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: Cribl
providerId: cribl
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:
  - Configuration
  - Data Lake
  - Data Pipelines
  - Data Routing
  - Edge Computing
  - Observability
  - Search
  - Stream Processing
  - Telemetry
  - Rate Limiting
  - Quotas
  - Throttling
description: Cribl's APIs (Cloud, Stream, Edge, Search, Lake, As Code) authenticate via OAuth 2.0 client
  credentials against the Cribl Cloud control plane. Cribl does not publish per-API-key request rate
  limits on its public documentation; effective throughput is bounded primarily by the platform-tier
  worker capacity (worker groups, worker processes, search executors) and daily TB/day data-processing
  ceiling. Hard request-rate throttles, if any, are enforced at the gateway and surfaced via standard
  HTTP 429 / 503 responses; exact numeric limits are not published.
sources:
  - https://docs.cribl.io/api-reference/
  - https://cribl.io/pricing/
responseCodes:
  throttled: 429
  serviceUnavailable: 503
limits:
  - name: Daily data processed (Free)
    scope: account
    metric: tb_per_day
    limit: 1
    timeFrame: day
    notes: Free tier ceiling for processed data volume. Enforced as a quota, not as a per-second throttle.
  - name: Daily data processed (Standard)
    scope: account
    metric: tb_per_day
    limit: 5
    timeFrame: day
    notes: Standard tier ceiling.
  - name: Worker processes (Free)
    scope: account
    metric: concurrent_workers
    limit: 10
    notes: Worker process ceiling that bounds concurrent pipeline throughput on the Free tier.
  - name: Worker processes (Standard)
    scope: account
    metric: concurrent_workers
    limit: 50
  - name: API request rate
    scope: api-key
    metric: varies
    limit: not publicly documented
    notes: Cribl Cloud API enforces gateway-level throttling but does not publish per-second numbers.
      Honor Retry-After when 429 is returned.
policies:
  - name: OAuth 2.0 client credentials
    description: All Cribl Cloud API calls authenticate with OAuth 2.0 client credentials; tokens are
      short-lived, so clients must cache and refresh access tokens rather than re-authenticating per
      request.
  - name: Backoff Strategy
    description: On 429 or 5xx responses, implement exponential backoff with jitter and respect Retry-After
      headers when present.
  - name: Capacity, not RPS
    description: Cribl's effective consumption ceiling is the tier-bound daily TB/day and worker capacity
      rather than a fixed requests-per-second budget. Scale by upgrading the tier or adding worker
      groups / processes / executors.
  - name: Edge fleet scoping
    description: For Cribl Edge, each edge node enforces its own local processing budget; control-plane
      API rate limits apply only to the Cloud / Stream / Edge management endpoints, not to the data
      path on the edge agents.
notes: Cribl does not publish concrete per-API-key requests-per-second limits in public documentation.
  This artifact captures the published tier-bound capacity ceilings and standard 429/Retry-After contract;
  reconciled is false until exact request-rate numbers are published.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com