# Best Voice Agent Platforms in 2026: Vapi vs Retell AI vs Bland AI vs LiveKit

> Vapi, Retell AI, Bland AI, LiveKit Agents, Pipecat, ElevenLabs Agents and OpenAI Realtime compared on build-vs-buy, telephony, custom LLMs and open source.

Vapi is the buy-side default when developers own the agent, Retell AI when an operations team does, and Bland AI when a regulated enterprise wants one vendor running its own models. Build on LiveKit Agents or Pipecat, both open source, when voice is the product. ElevenLabs Agents is voice-first; the OpenAI Realtime API is a model API, not a platform.

For most teams shipping a phone or web voice agent in 2026, the buy-side default is [Vapi](/tools/vapi) if developers own the project and [Retell AI](/tools/retell-ai) if an operations team does; [Bland AI](/tools/bland-ai) is the pick for regulated enterprises that want one vendor running its own models. When voice is the product and you want to own the pipeline, build on [LiveKit](/tools/livekit) Agents or [Pipecat](/tools/pipecat), the two open-source frameworks. [ElevenLabs](/tools/elevenlabs) Agents (branded ElevenAgents on the site as of October 2026) is the platform to choose when its voices are the point; the OpenAI Realtime API is a model API that several of these platforms expose, not a platform.

*Last reviewed: October 2026.*

Every platform here is usage-priced per minute (the OpenAI API per token) and the numbers change often, so this roundup quotes no prices; see each tool page for dated figures. We quote no latency or market-share claims either; every vendor publishes its own.

## The summary table

| Platform | Models | Build-vs-buy position | Telephony | Custom LLM / Claude | Open source? |
| --- | --- | --- | --- | --- | --- |
| [Vapi](/tools/vapi) | Your choice of STT, LLM and TTS providers | Buy, developer-first | Inbound and outbound numbers, bring your own carrier | Any OpenAI-compatible endpoint; Anthropic among the providers | No (open SDKs) |
| [Retell AI](/tools/retell-ai) | GPT, Claude, Gemini or speech-to-speech, per agent | Buy, operations-first | Retell numbers, Twilio, Vonage, any SIP trunk | Claude models listed; custom LLM over WebSocket | No (open SDKs) |
| [Bland AI](/tools/bland-ai) | Bland's own STT, LLM and TTS | Buy, regulated enterprise | Bland numbers, your Twilio, SIP trunks | Own LLM by default; custom models enterprise-only | No (open CLI and web SDK) |
| [LiveKit](/tools/livekit) Agents | Plugins for major providers, or LiveKit Inference | Build, framework plus optional cloud | Full telephony support | Any provider through plugins | Yes, Apache-2.0 |
| [Pipecat](/tools/pipecat) | Any provider through plugins | Build, Python pipeline framework | Not stated in our sources | Any LLM; Claude Code skills for scaffolding | Yes, BSD-2-Clause |
| ElevenLabs Agents (ElevenAgents) | In-house voices; LLM-agnostic | Buy, voice-first | Telephony with Twilio and Genesys connectors, SIP trunk | Bring your own model, or hosted models | No |
| OpenAI Realtime API | OpenAI speech-to-speech models | Model API, not a platform | SIP through a trunking provider | OpenAI models only | No |

## Buy, build, or just the model

The seven split into three postures, which the [realtime voice agents](/guides/voice/realtime-voice-apis) guide calls build, assemble and buy. Vapi, Retell, Bland and ElevenLabs are platforms: they own turn-taking, interruptions, telephony and the operations tooling, and you configure agents. LiveKit Agents and Pipecat are frameworks: you write the agent in Python or Node, choose every provider, and run it yourself or on their clouds. The OpenAI Realtime API sits underneath both camps as a speech-to-speech model you can call directly.

What divides them is less the feature list than who picks the model and who is on the hook when a call goes wrong.

## Vapi: the developer-first buy

Vapi describes itself as "the developer platform for building voice AI agents", and the design follows from that sentence. Every assistant combines three components, speech-to-text, an LLM and text-to-speech, and the docs promise "full control over each component, with dozens of providers and models to choose from". The LLM can be any OpenAI-compatible endpoint, which the docs list as "OpenRouter, AnyScale, Together AI, or your own server", and Anthropic is among the first-party providers. Assistants, Squads (multi-agent handoffs that keep context), tools and tests can be kept "as files in git", a config-as-code posture no other buy-side platform leads with.

MCP runs both ways: assistants connect to MCP servers for tools at runtime, and a Vapi MCP Server exposes the Vapi API to coding agents. The 2026 additions were Vapi Monitoring (April), simulations (August) and a Series B announced on May 12, 2026, led by Peak XV with YC, M12 and Kleiner Perkins.

**Verdict:** the buy-side pick for engineering teams. You get a live phone agent fast, keep model choice, and the agent lives in the repo rather than a dashboard. The trade is that operations features such as QA and campaigns are thinner than Retell's.

## Retell AI: the operations team's buy

Retell is the same shape as Vapi with the center of gravity moved to the people who run phone operations. The pitch is a drag-and-drop canvas where you "add functions, integrations, call transfers, DTMF, SMS, and custom logic", then "simulate thousands of scenarios, and turn real production calls into regression tests". Around it sit contact-center features: IVR detection, live listen-in and takeover, outbound campaigns, a built-in CRM (June 2026), an AI QA Analyst (January 2026) and Conductor (July 2026), which simulates proposed changes before they ship.

Model choice is explicit. Models are grouped into "versatile and highly intelligent", "fast and cost-efficient" and "speech to speech", with the per-minute price next to each, and the dropdown lists the GPT 5.x line, Claude 5 Sonnet, Claude 4.6 Sonnet, Claude 4.5 Sonnet and Gemini 3.5 Flash. Your own LLM plugs in over a WebSocket, one connection per call: Retell handles telephony, transcription and turn-taking while your server generates each reply. The catch is documented plainly: "The LLM playground can't test a custom LLM agent, and simulation and batch testing reject them."

MCP runs both ways here too. Agents can call a remote MCP server's tools during a live call, flows have an MCP node, and Retell's own MCP server plus a Claude connector let you build, test and analyze agents from Cursor, Claude Desktop, Claude Code or a Claude conversation. Compliance is HIPAA, GDPR and SOC 2 Type 1 and 2.

**Verdict:** the buy-side pick when an operations team will own the agent after launch. The flow builder, testing and QA are the differentiators; keep the model inside Retell's list if you want the testing tools.

## Bland AI: the enterprise stack on its own models

Bland makes the opposite bet to Vapi and Retell. Rather than orchestrating other vendors' models, it says it is "the only voice AI that runs entirely on its own models", with STT, LLM and TTS "built and run by one team", 40+ languages and real-time translation in 23 of them. Its pitch is regulated work: "Bland automates the calls where a single misstep can mean a lawsuit or a patient in danger", and it claims "230+ regulated companies". Enterprise customers get isolated, dedicated infrastructure, versioned Agent Releases, on-prem or VPC options and forward-deployed engineers. Compliance, per the pricing FAQ, covers SOC 2 Type I and II, HIPAA with a BAA, GDPR with a DPA, PCI DSS self-attested, FedRAMP 20x Class A and ISO 27001.

Two 2026 changes matter. Norm (March) is an assistant that "builds, edits, tests, and debugs your agents" from a plain-English description. The new dashboard (October 13) replaces pathways and personas with a single agent that has dev, staging and production environments, versions and branches, and Bland says all production pathways and personas must be migrated by November 15. The Bland MCP server (Streamable HTTP, OAuth sign-in from ChatGPT, Claude and Claude Code, or an API key) lets a coding agent place calls, build pathways, run evals and query analytics. Custom or fine-tuned LLMs are an enterprise conversation, not a self-serve setting.

**Verdict:** the pick when a regulated buyer wants one vendor accountable for every layer, and the wrong pick when you want to choose or swap the LLM yourself.

## LiveKit Agents: the open-source build

LiveKit Agents is the build posture's default. "The Agents framework lets you add any Python or Node.js program to LiveKit rooms as full realtime participants", and the whole ecosystem is "open source under the Apache 2.0 license"; the agents repository had about 14,900 stars as of October 2026, with `livekit-agents@1.8.8` released on 2026-10-15. You bring models through plugins "for most major AI providers", or use LiveKit Inference on LiveKit Cloud without separate API keys. The framework ships a custom turn-detection model, multi-agent handoff, and "built-in agent server orchestration, load balancing, and Kubernetes compatibility", plus "full support for telephony, so the user can join the call from a phone". Deploy to LiveKit Cloud or any custom environment; a no-code Agent Builder covers browser prototyping.

**Verdict:** the choice when voice is core product and you want control over every stage and the unit economics that come with running it. Budget real engineering time; the payoff is a stack you own.

## Pipecat: the open-source pipeline

Pipecat is "an open-source Python framework for building real-time voice and multimodal conversational agents", BSD-2-Clause, "maintained by Daily and the community", with about 16,700 stars as of October 2026 and v1.13.0 released on 2026-10-19. It composes a pipeline from interchangeable STT, LLM and TTS pieces over WebSocket or WebRTC transports, supports "a full multi-agent system where specialists hand off, fan out in parallel, and coordinate over a shared bus", and ships client SDKs from JavaScript and React to Swift, Kotlin, C++ and ESP32. Around it sit `pipecat init quickstart`, Pipecat Flows, the Whisker debugger and Pipecat Cloud. It is also the most coding-agent-friendly entry: Pipecat Skills install into Claude Code with `claude plugin marketplace add pipecat-ai/skills`, and `pipecat init` lets Claude Code or Codex build the project for you.

**Verdict:** the build-side choice when the pipeline is your differentiation and you do not want to adopt a media-server worldview. It pairs with LiveKit or other transports underneath; the [voice agent pipeline](/guides/voice/build-a-voice-agent) guide walks through the stages it orchestrates.

## ElevenLabs Agents (ElevenAgents): voices first

ElevenLabs renamed Conversational AI to "ElevenLabs Agents" on 2025-09-03, and as of October 2026 its product page and docs brand it "ElevenAgents"; we found no dated announcement for that second name. The product promises agents "in 90+ languages" across "telephony, web, mobile, WhatsApp, SMS, email, and chat", with native connectors for Twilio, Genesys, Zendesk and Salesforce and a SIP trunk option. It is "LLM agnostic - bring your own model, call a frontier model via API, or use our hosted, domain-tunable models", reaches external systems "through MCP, APIs, and webhooks", and agents can be created and updated "from any MCP client". The voices are the draw: a library of over 16,000, cloning and design, and models built in-house. Compliance covers SOC 2 Type II, ISO 27001, PCI DSS Level 1, HIPAA and GDPR, with zero-retention mode and US, EU and India data residency.

**Verdict:** the buy-side pick when voice quality and multilingual reach are the product requirement, and a strong option when you already pay ElevenLabs for TTS. For voice-quality comparisons, see the [TTS API roundup](/guides/voice/best-tts-apis-2026).

## OpenAI Realtime API: the model, not the platform

The Realtime API is how you "build a speech-to-speech voice agent" on OpenAI's models directly; the documentation sample uses `gpt-realtime-2.1`, which takes text, audio and image in and returns text and audio. Sessions run "over WebRTC in the browser or WebSocket on the server", and a phone number can reach the API over SIP through "a SIP trunking provider (e.g., Twilio)". Tools come from "functions, MCP servers, and connectors". The API is generally available, and OpenAI tells integrations built on the earlier interface to migrate.

What it lacks is everything the platforms above sell: campaigns, QA, live monitoring, flow builders, regression tests. That is why Retell lists "GPT Realtime 2.1" and "GPT Realtime mini" as speech-to-speech options and Open WebUI's v0.12.0 realtime calls run on it.

**Verdict:** build on it directly if you want the fewest moving parts, OpenAI models and your own operations tooling; otherwise reach it through a platform.

## How to choose

- **Developers own the agent and you want to ship this week:** Vapi. Keep the assistant in git and swap models.
- **An operations team will run the agent after launch:** Retell AI. Use the flow builder, simulation and QA, and stay on its model list.
- **A regulated buyer wants one accountable vendor and dedicated infrastructure:** Bland AI. Accept that the LLM is Bland's, and plan the November 15 migration if you are on pathways today.
- **Voice is the product and you want to own the stack:** LiveKit Agents for the full open-source platform with telephony, Pipecat for a pipeline framework that leaves transport choices open.
- **Voice quality and languages are the requirement:** ElevenLabs Agents.
- **You want the fewest moving parts on OpenAI models:** the Realtime API directly, with SIP for phones.
- **You need Claude specifically:** Retell lists Claude models, Vapi mixes Anthropic with any STT and TTS, ElevenLabs is LLM-agnostic, and both open-source frameworks take it through plugins.

Whatever you choose, cost it with platform fee, model pass-through and telephony as separate line items; a headline per-minute number hides the comparison.

## Continue exploring

- [How to build a voice agent](/guides/voice/build-a-voice-agent) covers the pipeline, the latency budget and turn-taking.
- [Realtime voice agents](/guides/voice/realtime-voice-apis) goes deeper on the build, assemble and buy postures.
- The [TTS API](/guides/voice/best-tts-apis-2026) and [STT API](/guides/voice/best-stt-apis-2026) roundups cover the providers the open frameworks orchestrate, including [Cartesia](/tools/cartesia) and [Deepgram](/tools/deepgram).
- The [voice-agent-engineer](/agents/data-ai/voice-agent-engineer) agent builds the self-hosted loop end to end.

## Sources and further reading

- [Vapi documentation: Introduction](https://docs.vapi.ai/quickstart/introduction) — Vapi
- [Vapi: Custom LLM (OpenAI-compatible endpoints)](https://docs.vapi.ai/customization/custom-llm/fine-tuned-openai-models) — Vapi
- [Retell AI: Integrate your own LLM](https://docs.retellai.com/integrate-llm/overview) — Retell AI
- [Retell AI: MCP for single- and multi-prompt agents](https://docs.retellai.com/build/single-multi-prompt/mcp) — Retell AI
- [Bland: Enterprise Voice AI Platform for Phone Agents](https://www.bland.ai/) — Bland
- [Bland MCP server overview](https://docs.bland.ai/integrations/mcp/overview) — Bland
- [LiveKit Agents documentation](https://docs.livekit.io/agents) — LiveKit
- [pipecat-ai/pipecat README](https://github.com/pipecat-ai/pipecat) — Daily (GitHub)
- [ElevenLabs Agents](https://elevenlabs.io/agents) — ElevenLabs
- [OpenAI Realtime API guide](https://developers.openai.com/api/docs/guides/realtime) — OpenAI

---

_Source: https://agentscamp.com/guides/comparisons/best-voice-agent-platforms-2026 — Guide on AgentsCamp._
