Livekit Rate Limits
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.
Livekit Rate Limits is the machine-readable rate-limit profile for LiveKit on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 3 rate-limit definitions, measuring concurrent_participants, concurrent_jobs, and concurrent_sessions.
The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Realtime, WebRTC, and Rate Limiting.
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/livekit-rate-limits"curl "https://apis.io/api/v1/rate-limits?limit=25"Discovery needs no key. Ratings and market analysis are Pro.