# LiveKit Agents — Open-source Python and Node.js framework for voice AI agents, with LiveKit Cloud hosting, telephony and observability. > Source: The Agents Index — https://theagentsindex.com/livekit-agents (structured, researched, re-verified) > Facts last verified: 2026-09-02 LiveKit Agents is a framework for building realtime voice agents in Python or Node.js, connecting speech-to-text, an LLM and text-to-speech into a single session. LiveKit Cloud deploys and scales those agents on its WebRTC and SIP network. | Fact | Value | | --- | --- | | Website | https://livekit.com/voice-agents | | Price | from $50/month | | Free tier | Yes | Build plan, $0/mo, no credit card: 1,000 agent session minutes, 5 concurrent agent sessions, 1 deployment, $2.50 in LiveKit Inference credits (~50 minutes), 1 free US local number with 50 inbound minutes, 5,000 WebRTC participant minutes, 100 concurrent connections, 50 GB egress, 1,000 minutes of session recordings, 100,000 observability events. Community support only; no custom voices, no cold-start prevention, no instant rollback. The allowance is a hard cap: 'For projects on the free Build plan, the included allowance acts as a hard cap — after you exceed it, new requests fail rather than incurring overage charges.' Allowances reset monthly and do not roll over, and all of a user's free projects share one allowance. ## What it does **Done-for-you service** · No — You run the software: an open-source SDK plus a self-serve cloud. Enterprise adds a designated solutions engineer, which is support, not a build-for-you engagement. > LiveKit is a developer platform for voice, video, and physical AI. Build agents with our open source SDKs, deploy them across a global network of data centers, and monitor them in production > — https://livekit.com/products/agent-platform · Hero section, paragraph under 'Build, run, and observe AI agents' ## How much it does unattended **Runs autonomously** · Yes — Agents run as server-side workers dispatched into a live session, handling calls end to end and handing off to a human only when the flow transfers. > voice agents can handle inbound calls, make outbound calls, transfer to humans, and interact with traditional telephony systems. LiveKit supports this natively. > — https://livekit.com/voice-agents · Frequently asked questions, 'Can voice agents make and receive phone calls?' **Multi-agent** · Yes — Multiple agents in one session via handoffs, plus a supervisor pattern where one agent keeps control and delegates to scoped tasks. > The LiveKit Agents framework lets you build sophisticated voice AI apps with multiple personas, conversation phases, or specialized capabilities using agents, handoffs, and tasks. > — https://docs.livekit.io/agents/logic/workflows.md · Overview, first paragraph **Agent permissions** · Partly — No built-in human-approval gate: the model calls whichever tools the developer exposes. Bounding is by construction: MCP toolsets can be filtered by tool name or set to require confirmation on a duplicate call. > Tool invocations are model-driven: the LLM chooses to call them based on context, and the returned results are fed back to the model for continued reasoning. > — https://docs.livekit.io/agents/logic/workflows.md · Core constructs, Tools bullet ## Which models it runs on **Claude** · Yes — Anthropic plugin for Python and Node.js, using your own Anthropic API key. Claude is not among the models served through LiveKit Inference, so it is a plugin-only path. > This plugin allows you to use the Claude API as an LLM provider for your voice agents. > — https://docs.livekit.io/agents/models/llm/anthropic.md · Overview, first sentence **GPT** · Yes — GPT-4o, GPT-4.1 and the GPT-5 families are served through LiveKit Inference with no separate OpenAI key, or via the OpenAI plugin on your own account. > OpenAI models are available in LiveKit Agents through LiveKit Inference and the OpenAI plugin. > — https://docs.livekit.io/agents/models/llm/openai.md · Overview, first sentence **Open models** · Yes — Open-weight models are the recommended default in LiveKit Inference (Gemma 4 31B, GPT OSS 120B, DeepSeek), and the Ollama plugin runs models locally. > Gemma 4 31B is the recommended default LLM. It's a latency-optimized, open-weight model served on LiveKit's infrastructure. > — https://docs.livekit.io/agents/models/llm/ · LiveKit Inference section, 'Recommended for voice agents' callout **Model choice** · Yes — You pick every stage. STT, LLM and TTS are swappable through the plugin system, and realtime speech-to-speech models can replace the three-stage pipeline. > LiveKit works with all major STT, LLM, and TTS providers through a plugin system. Swap models in and out with a few lines of code. > — https://livekit.com/voice-agents · Why build voice agents with LiveKit?, 'Unified model access' ## Where you use it **On the command line** · Yes — The lk CLI creates projects, deploys agents and manages LiveKit Cloud; agents can also be run and talked to locally in console mode. > The LiveKit CLI (lk) is the primary interface for managing LiveKit Cloud projects, creating applications from templates, and deploying agents. > — https://docs.livekit.io/reference/developer-tools/livekit-cli.md · Overview, first paragraph **In your pipeline** · Partly — CI is a deployment surface, not an acting surface: an official GitHub Action deploys the agent on push. The agent itself never acts on a pull request. > To deploy from CI instead of running lk agent deploy by hand, use the livekit/deploy-action GitHub Action. Use it to deploy your agent whenever code is pushed to your main branch. > — https://docs.livekit.io/deploy/agents/managing-deployments.md · Deploy with GitHub Actions section **In a browser** · Yes — Agent Console in LiveKit Cloud runs and debugs a deployed agent in the browser; Agent Builder prototypes one with no code, and the dashboard is on every plan. > Agent Console lets you test and debug cloud-deployed voice agents in your browser. > — https://livekit.com/voice-agents · How to get started with voice agents, 'Test in Console' ## Whose machine it runs on **Self-hosted** · Yes — Agents are containers you can run on your own Kubernetes; the LiveKit media server and SIP service are separately self-hostable. Self-hosted agents still meter WebRTC participant minutes if they connect to LiveKit Cloud. > LiveKit Agents run as containers, so you can deploy them to LiveKit Cloud or to any Kubernetes cluster or similar container orchestration platform. > — https://docs.livekit.io/deploy/custom/deployments.md · Where to deploy section **Open source** · Yes — Apache 2.0 for the Agents SDK and for the media server, SIP, Egress, Ingress and client SDKs. LiveKit Cloud is the commercial hosted layer on top. > The LiveKit Agents SDK is open source under the Apache 2.0 license. You can self-host or deploy to LiveKit Cloud for managed infrastructure. > — https://livekit.com/voice-agents · Frequently asked questions, 'Is LiveKit's agent framework open source?' ## What it costs to run **How it meters** · Yes — Monthly plan fee plus consumption: $0.01 per agent-session minute, per-token LLM, per-1M-character TTS, per-minute STT and telephony. Each plan bundles an allowance before overage starts. > Most features are also metered: you're billed per unit of consumption, with an included monthly allowance on each plan. > — https://docs.livekit.io/deploy/admin/quotas-and-limits.md · Overview, first paragraph **Free tier** · Yes — Build plan is $0/mo with no card, including 1,000 agent-session minutes, one deployment and $2.50 of inference credits. > NO CREDIT CARD REQUIRED $0/mo > — https://livekit.com/pricing · Plan cards, Build column price block **API access** · Yes — Server APIs for rooms, participants, tracks, SIP and Egress, driven from your backend with signed tokens, at 1,000 requests per minute per project. Metrics export APIs are Scale and above. > LiveKit has built-in APIs that let you manage rooms, participants, and tracks. These APIs are designed for use by your backend and are fully distributed across multiple nodes > — https://docs.livekit.io/reference/other/roomservice-api.md · Overview, first paragraph **MCP server** · Partly — The agent is the MCP client: it consumes tools from remote HTTP or local stdio MCP servers, Python only. LiveKit does not expose a running agent as an MCP server for another agent to query. > LiveKit Agents has first-class support for Model Context Protocol (MCP) servers. > — https://docs.livekit.io/agents/logic/tools/mcp.md · Overview, first sentence **Bring your own key** · Partly — Provider plugins run on your own account, key and billing, and self-hosted agents run in your own cloud. Bringing your own key to traffic routed through LiveKit Inference is not supported. > Use the plugin instead if you prefer to manage billing and rate limits yourself, or need access to a provider not currently available through LiveKit Inference. > — https://docs.livekit.io/agents/models/llm/ · Overview, second paragraph ## Buying it for a team **A company can buy it** · Yes — Paid plans are self-serve by card; Enterprise is quoted, adds non-credit-card billing and a support SLA, and requires an annual commitment. Team collaboration starts on Ship. > Enterprise plans can be configured with custom limits well above the published Build, Ship, and Scale numbers. They come with an annual commitment > — https://docs.livekit.io/deploy/admin/quotas-and-limits.md · Enterprise plans section **Seat model** · No — Not seat-priced. Plans are per project with usage allowances, and neither the plan cards nor the feature matrix publishes a seat count, floor or ceiling; dashboard users get admin, write or read roles. > LiveKit Cloud applies quotas to each project — limits on concurrency, request rates, session durations, and other per-project operations. > — https://docs.livekit.io/deploy/admin/quotas-and-limits.md · Overview, first paragraph **Pooled budget** · Partly — No per-user balances: allowances pool inside a project. Sharing one plan across projects, and quotas managed at workspace level, are Enterprise only. > On the Enterprise plan, quotas are managed at the workspace level. > — https://docs.livekit.io/deploy/admin/quotas-and-limits.md · Overview, 'Workspace quotas (Enterprise)' note **Admin controls** · Partly — Three dashboard roles only, and the role-based access row on the plan matrix is No for Build and Ship, Yes from Scale. Agent capability is bounded in code, not by console policy. > Role-based access control. LiveKit's dashboard currently supports admin, write, and read roles. We are actively expanding RBAC; finer-grained roles will be documented here as they ship. > — https://livekit.com/security/overview · Access control section, 'Role-based access control' **Audit log** · Partly — Config changes and observability access are logged internally, but there is no customer-facing audit log export; SIEM export is roadmap only and handled by the account team. > Audit logging. Access to observability data and modifications to project configuration are logged. Audit log export to external SIEMs (Splunk, Datadog, etc.) is on our roadmap > — https://livekit.com/security/overview · Access control section, 'Audit logging' **Single sign-on** · Partly — SAML SSO exists but only on Enterprise; every lower tier authenticates to the dashboard with Google, GitHub OAuth or email. No OIDC is claimed. > Single sign-on. SAML-based SSO is available on the Enterprise tier and supports common identity providers including Okta, Microsoft Entra ID, and Google Workspace. > — https://livekit.com/security/overview · Access control section, 'Single sign-on' ## What happens to your code **Opt out of training** · Yes — Nothing to opt out of: zero retention is the default on every plan, LiveKit logs no prompts, audio or completions, and voice-clone samples are opted out of provider training on your behalf. > Sub-processors do not retain, log, or use customer inference traffic for training or model improvement. > — https://livekit.com/security/overview · AI and inference data section, 'Zero retention by sub-processors' **Data residency** · Partly — US, EU and India, configurable per project, though the region pinning row on the plan matrix is No for Build and Ship, Yes from Scale. Single-tenant deployments are not offered. > Customers can pin media routing, observability data, agent hosting, and stored data to a region. Today, supported regions include the United States, the European Union, and India. > — https://livekit.com/security/overview · Infrastructure section, 'Data residency' **Getting out** · Partly — Recordings go straight to your own S3, GCS or Azure bucket and traces export to any OpenTelemetry backend, but unused inference credits expire monthly, observability data is kept 30 days, and metrics export APIs are Scale and above. > Unused credits do not roll over to the next month. > — https://docs.livekit.io/deploy/admin/quotas-and-limits.md · Metered resources section, 'Inference credits' tip **Certifications** · Partly — SOC 2 Type II active, GDPR and CCPA/CPRA compliant, EU-US DPF certified; ISO 27001 and PCI DSS still in progress, HIPAA BAAs only for Scale and Enterprise, and the security reports row is Scale and above. > LiveKit's security measures are vetted by reputable third-party auditors. PCI DSS and ISO 27001 are in progress. Audit artifacts are available under NDA via the Trust Center. > — https://livekit.com/security · Industry-standard compliance section, intro paragraph ## Platform record (as of 2026-08-30) Reported by the code-hosting platform, not by the vendor. | Fact | Value | | --- | --- | | Licence | Apache-2.0 | | Stars | 13594 | | Forks | 3646 | | Last push | 2026-08-30 | ## Provenance 1 of 22 sources behind the facts above are independent of the vendor. ## Coverage elsewhere Pages about this product that the vendor does not control. The label states how independent each one is. | Source | Kind | Read | | --- | --- | --- | | techcrunch.com | Independent source | 2026-08-23 | ## What changed - 2026-09-02 — Capabilities · Commercial terms · Free tier - 2026-08-31 — Capabilities · Commercial terms · Free tier · Price - 2026-08-23 — Alternatives · Documentation link · One-liner · Summary ## Correcting this record Anything marked "Not established" is a question we have not answered — it is not a No. If you represent LiveKit Agents, or anything here is wrong or out of date, you can supply it with a source: the operations this site accepts from an agent are listed at https://theagentsindex.com/.well-known/agents.json — that catalogue needs no key to read, and each entry states its own auth. Supplying evidence is free. Nothing that can be bought here changes what a field says, whether a gap is closed, or how this record is scored.