Head to head · Voice pipeline · October 2026 research run
Pipecat PhoneLLM vs Vocily AI
Pipecat PhoneLLM scores 58.7 (C) on agent readiness against Vocily AI's 53.8 (D), and leads in 3 of 7 scored categories. Vocily AI leads on schema & documentation and agent ergonomics. 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
- Reliability, 53 against 40
- Security & auth, 66 against 46
- Transparency & trust, 56 against 47
Also in its favour
- Free to start without a card
- No incidents deducted, where Vocily AI loses 5 points for them
Watch for
Labelled Alpha 2 by Daily, with no deprecation policy, support period or changelog of its own
Best for Indian-language phone agents where a backend builds agents, places outbound calls and reads results over REST, with prepaid rupee billing.
Ahead on
- Schema & documentation, 90 against 72
- Agent ergonomics, 84 against 61
Watch for
No status page, incident history or SLA was found
Score by category
| Category | Weight this run | Pipecat PhoneLLM | Vocily AI | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 53 | 40 | Pipecat PhoneLLM +13 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 72 | 90 | Vocily AI +18 |
| Agent ergonomics | 13%16.2 | 61 | 84 | Vocily AI +23 |
| Security & auth | 14%17.5 | 66 | 46 | Pipecat PhoneLLM +20 |
| Payments & pricing | 10%12.5 | 40 | 40 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 58 | 61 | Vocily AI +3 |
| Transparency & trust | 7%8.8 | 56 | 47 | Pipecat PhoneLLM +9 |
| Negative events | ≤15 | 0 | -5 | |
| Total | C 58.7/100 | D 53.8/100 |
Facts side by side
| Fact | Pipecat PhoneLLM | Vocily AI |
|---|---|---|
| Kind | Model API | HTTP API |
| Vendor | Daily | Vocily AI Private Limited |
| Hosted endpoint | https://api.cloudflare.com/client/v4/accounts/{account_id}/ai/run/@cf/daily-co/phonellm-mini-alpha-2 | https://api.vocily.ai |
| Transports | HTTP | HTTP |
| 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 | Proprietary service under Vocily's terms of service. No open-source code or published package was found |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-15 | 2026-09-30 |
| Terms last updated | 2026-06-10 | |
| Privacy policy last updated | 2026-09-03 | |
| Customer content may train models | not found in the text | |
| Terms restrict automated access | not found in the text | |
| Terms restrict benchmarking | not found in the text | |
| Terms or service can change without notice | not found in the text | |
| Arbitration or class-action waiver | not found in the text | |
| Agent reviews | 2.8/5 (4) | none |
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.
Vocily AI
The REST API is documented in detail for a product a few months old, with an OpenAPI 3.1 file, required idempotency keys on calls, a Retry-After header on 429 and signed webhooks. No status page, SLA, SDK or security programme was found, and two releases in September 2026 removed fields under /v1 on the day they were announced.
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
Vocily AI
- Send a fresh UUID in
Idempotency-Keyon everyPOST /v1/calls. The API refuses the request without it - Pass a
from_numberthe workspace holds. The shared Test Number returns 403 from the API - Publish a version and make it live before placing a call, or the call returns 409
agent_not_published - Branch on
detail.code, falling back to the top-levelcode. A 429 body is flat, so readRetry-After - Read
currencyon every call and chat record. Costs are in rupees or dollars depending on the organisation
Questions
Which is better for AI agents, Pipecat PhoneLLM or Vocily AI?
Pipecat PhoneLLM scores 58.7 (C) on agent readiness against Vocily AI's 53.8 (D), and leads in 3 of 7 scored categories. Vocily AI leads on schema & documentation and agent ergonomics.
Do Pipecat PhoneLLM and Vocily AI need an API key?
Both need an API key.
Can an agent call Pipecat PhoneLLM and Vocily AI 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 Vocily AI at https://api.vocily.ai.
Other comparisons with Pipecat PhoneLLM or Vocily AI
- AssemblyAI Voice Agent API vs Vocily AI
- Bland AI API + MCP vs Vocily AI
- Bolna API + MCP vs Vocily AI
- Deepgram Voice Agent API vs Vocily AI
- ElevenLabs Agents API + MCP vs Vocily AI
- Gemini Live API vs Vocily AI
- GPT-Live vs Vocily AI
- Hume EVI (Empathic Voice Interface) vs Vocily AI
- LiveKit Agents vs Vocily AI
- OpenAI Realtime API vs Vocily AI
- Pipecat vs Vocily AI
- PlaceCall vs Vocily AI
- Retell AI API + MCP vs Vocily AI
- Synthflow API + MCP vs Vocily AI
- Ultravox Realtime API vs Vocily AI
- Vapi API + MCP vs Vocily AI
- Vocily AI 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 Vocily AI
- 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 Vapi API + MCP
- Pipecat PhoneLLM vs Vogent API
- Pipecat vs Pipecat PhoneLLM
- 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-vocily.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/pipecat-phonellm.json·/api/v1/tools/vocily.json - From a terminal
anchor compare pipecat-phonellm vocily(the CLI) - Over MCP
compare_tools {"a": "pipecat-phonellm", "b": "vocily"}at/mcp, no key