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: LiveKit
providerId: livekit
created: '2026-05-08'
# Provenance stamped 2026-08-11: this artifact was written by the API Evangelist
# bulk sweep dated 2026-05-08, not harvested from the provider. See roadmap#35.
method: generated
modified: '2026-05-08'
reconciled: false
tags:
  - Realtime
  - WebRTC
  - Rate Limiting
description: >-
  LiveKit Cloud caps are tier-dependent and usage-driven. Common caps include max concurrent
  participants per room, max simultaneous rooms, max egress jobs in flight, and Agents session
  concurrency. Self-hosted LiveKit limits are operator-controlled by VM and SFU sizing.
notes: Cloud tier caps not published as a public table; figures are typical defaults.
sources:
  - https://docs.livekit.io/home/cloud/quotas/
responseCodes:
  throttled: 429
limits:
  - name: Participants per room (typical default)
    scope: room
    metric: concurrent_participants
    limit: 1000
  - name: Simultaneous Egress jobs (typical)
    scope: project
    metric: concurrent_jobs
    limit: 25
  - name: Agents concurrent sessions (typical)
    scope: project
    metric: concurrent_sessions
    limit: 100
    notes: Tier-dependent; raised under Scale plan.
policies:
  - name: Room sharding
    description: For very large rooms, shard participants across multiple LiveKit rooms with media-server fanout.
  - name: Backoff Strategy
    description: Honor 429 Retry-After and apply exponential backoff with jitter on Twirp calls.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com