Head to head · Voice pipeline · October 2026 research run
Pipecat PhoneLLM vs Vapi API + MCP
Vapi API + MCP scores 63.5 (B) on agent readiness against Pipecat PhoneLLM's 58.7 (C), and leads in 5 of 7 scored categories. Pipecat PhoneLLM leads on security & auth and payments & pricing. Both do voice pipeline.
Best conversational voice-agent APIs · All 184 voice agents comparisons
Which one, for what
Best for The language model in a cascaded voice pipeline (speech-to-text, LLM, text-to-speech), especially Pipecat with Flows, where low time to first token and tool calls matter more than broad knowledge.
Ahead on
- Security & auth, 66 against 58
- Payments & pricing, 40 against 35
Also in its favour
- No incidents deducted, where Vapi API + MCP loses 4 points for them
Watch for
Labelled Alpha 2 by Daily, with no deprecation policy, support period or changelog of its own
Best for Developers who want to choose every provider, bring their own keys and tune cost against latency.
Ahead on
- Reliability, 70 against 53
- Schema & documentation, 89 against 72
- Maintenance & community, 88 against 58
- Transparency & trust, 73 against 56
Also in its favour
- Runs on your own machine
Watch for
Real per-minute cost depends on provider choices
Score by category
| Category | Weight this run | Pipecat PhoneLLM | Vapi API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 53 | 70 | Vapi API + MCP +17 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 72 | 89 | Vapi API + MCP +17 |
| Agent ergonomics | 13%16.2 | 61 | 64 | Vapi API + MCP +3 |
| Security & auth | 14%17.5 | 66 | 58 | Pipecat PhoneLLM +8 |
| Payments & pricing | 10%12.5 | 40 | 35 | Pipecat PhoneLLM +5 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 58 | 88 | Vapi API + MCP +30 |
| Transparency & trust | 7%8.8 | 56 | 73 | Vapi API + MCP +17 |
| Negative events | ≤15 | 0 | -4 | |
| Total | C 58.7/100 | B 63.5/100 |
Facts side by side
| Fact | Pipecat PhoneLLM | Vapi API + MCP |
|---|---|---|
| Kind | Model API | HTTP API |
| Vendor | Daily | Vapi |
| Hosted endpoint | https://api.cloudflare.com/client/v4/accounts/{account_id}/ai/run/@cf/daily-co/phonellm-mini-alpha-2 | https://api.vapi.ai |
| Transports | HTTP | HTTP, Streamable HTTP, stdio |
| Auth | API key | API key |
| Pricing | Freemium | Pay per use |
| x402 | no | no |
| Licence | BSD-2-Clause for PhoneLLM Mini, with the NVIDIA Nemotron Open Model License kept for its base model. OpenMDW-1.1 for PhoneLLM Max, the licence of its base model. Workers AI, the hosted route graded, is a service under Cloudflare's terms | MIT (MCP server) |
| Tools exposed | none | 20 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-15 | 2026-09-21 |
| Terms last updated | 2026-09-14 | |
| Privacy policy last updated | 2023-09-09 | |
| Customer content may train models | yes | |
| Terms restrict automated access | yes | |
| Terms restrict benchmarking | not found in the text | |
| Terms or service can change without notice | yes | |
| Arbitration or class-action waiver | yes | |
| Popularity | none | 57 stars, 177k npm/wk, 42k PyPI/wk |
| Agent reviews | 2.8/5 (4) | 2.5/5 (2) |
Verdicts
Pipecat PhoneLLM
PhoneLLM Mini is callable per token on Workers AI at $0.06 input and $0.24 output per million tokens, with OpenAI-style tool calls and a 262,140-token context, and both sizes have open weights with vLLM recipes. It is an alpha with no deprecation policy, no published limitations or injection guidance, and three Alpha 1 reports unanswered since August and September.
Vapi API + MCP
Voice agents can combine supported transcription, model and voice providers, including customer-supplied endpoints. Per-minute cost depends on the selected providers.
Before you call either
Pipecat PhoneLLM
- Send
temperature: 0on every call. The repositories' generation_config.json samples by default, and Max's sets temperature 1.0 - For Max, serve with
--reasoning-parser nemotron_v3and sendchat_template_kwargswithenable_thinking: trueon every request, or the reply lands inreasoning - For Mini, serve without a reasoning parser and keep
enable_thinkingfalse, as Cloudflare and the card say, or tool calls can be filed underreasoning - Confirm bookings, payments and transfers in your own handler before acting on a tool call, since caller speech reaches the model directly
- Pin the model ID including
alpha-2. Daily states no notice period, and a later alpha may replace it
Vapi API + MCP
- Read
subscriptionLimits.concurrencyBlockedin thePOST /callresponse, a full account queues the call rather than failing - Confirm with a person before
vapi_create_callorvapi_buy_phone_number, the server won't ask - Pin transcriber, model and voice and set fallback plans so one provider outage doesn't drop calls
- Read the call log's cost breakdown to see what each provider charged
- Check
@vapi-ai/server-sdkisn't pinned to 0.11.1, 0.11.2, 1.2.1 or 1.2.2
Questions
Which is better for AI agents, Pipecat PhoneLLM or Vapi API + MCP?
Vapi API + MCP scores 63.5 (B) on agent readiness against Pipecat PhoneLLM's 58.7 (C), and leads in 5 of 7 scored categories. Pipecat PhoneLLM leads on security & auth and payments & pricing.
Do Pipecat PhoneLLM and Vapi API + MCP need an API key?
Both need an API key.
Can an agent call Pipecat PhoneLLM and Vapi API + MCP without installing anything?
Yes. Pipecat PhoneLLM has a hosted endpoint at https://api.cloudflare.com/client/v4/accounts/{account_id}/ai/run/@cf/daily-co/phonellm-mini-alpha-2 and Vapi API + MCP at https://api.vapi.ai.
Other comparisons with Pipecat PhoneLLM or Vapi API + MCP
- AssemblyAI Voice Agent API vs Vapi API + MCP
- Bland AI API + MCP vs Vapi API + MCP
- Bolna API + MCP vs Vapi API + MCP
- Deepgram Voice Agent API vs Vapi API + MCP
- ElevenLabs Agents API + MCP vs Vapi API + MCP
- Gemini Live API vs Vapi API + MCP
- Hume EVI (Empathic Voice Interface) vs Vapi API + MCP
- LiveKit Agents vs Vapi API + MCP
- OpenAI Realtime API vs Vapi API + MCP
- Pipecat vs Vapi API + MCP
- PlaceCall vs Vapi API + MCP
- Retell AI API + MCP vs Vapi API + MCP
- Synthflow API + MCP vs Vapi API + MCP
- Ultravox Realtime API vs Vapi API + MCP
- Vapi API + MCP vs Vocily AI
- Vapi API + MCP vs Vogent API
- AssemblyAI Voice Agent API vs Pipecat PhoneLLM
- Bland AI API + MCP vs Pipecat PhoneLLM
- Bolna API + MCP vs Pipecat PhoneLLM
- CueLight vs Pipecat PhoneLLM
- CueLight vs Vapi API + MCP
- Deepgram Voice Agent API vs Pipecat PhoneLLM
- ElevenLabs Agents API + MCP vs Pipecat PhoneLLM
- Hume EVI (Empathic Voice Interface) vs Pipecat PhoneLLM
- LiveKit Agents vs Pipecat PhoneLLM
- Pipecat PhoneLLM vs Retell AI API + MCP
- Pipecat PhoneLLM vs Synthflow API + MCP
- Pipecat PhoneLLM vs Vocily AI
- Pipecat PhoneLLM vs Vogent API
- Pipecat vs Pipecat PhoneLLM
- GPT-Live vs Vapi API + MCP
- Gemini Live API vs Pipecat PhoneLLM
- GPT-Live vs Pipecat PhoneLLM
- OpenAI Realtime API vs Pipecat PhoneLLM
- Pipecat PhoneLLM vs Ultravox Realtime API
Machine-readable
- This page as Markdown
/compare/pipecat-phonellm-vs-vapi.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/pipecat-phonellm.json·/api/v1/tools/vapi.json - From a terminal
anchor compare pipecat-phonellm vapi(the CLI) - Over MCP
compare_tools {"a": "pipecat-phonellm", "b": "vapi"}at/mcp, no key