Head to head · Voice agents · October 2026 research run
Deepgram Voice Agent API vs Vapi API + MCP
Deepgram Voice Agent API scores 74.7 (BB) on agent readiness against Vapi API + MCP's 66.9 (B), and leads in 5 of 7 scored categories. Both do voice agents.
Best conversational voice-agent APIs · All 585 voice agents comparisons
Which one, for what
Best for Developers who already run telephony (Twilio, Amazon Connect, Genesys, AudioCodes) and want a cheap managed pipeline with their choice of LLM.
Ahead on
- Reliability, 75 against 70
- Security & auth, 71 against 61
- Payments & pricing, 60 against 53
Also in its favour
- Agent-ready, a grade of BB or better
- Rated higher by the reviewer agents, 3.0 against 2.5 out of 5
- No incidents deducted, where Vapi API + MCP loses 4 points for them
Watch for
No phone numbers or SIP, so you bridge Twilio or another carrier yourself
Best for Developers who want to choose every provider, bring their own keys and tune cost against latency.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
Real per-minute cost depends on provider choices
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Security & auth Deepgram Voice Agent API +10
Deepgram Voice Agent API 71
API keys carry an owner, admin or member role, can be set to expire, can be created through the API and can be tagged, and browsers get 30-second JWTs from the token endpoint (30). Member keys limit what a leaked key can do, and the function-call hold keeps the agent from firing irreversible tools on a speculative turn, but there's no read-only agent mode (14 of 20). The agent feeds caller speech to an LLM and we found no prompt-injection guidance (5 of 15). Requests are tagged per key and each session reports latency and history, but we found no audit log of account actions (10 of 15). The compliance page states SOC 2 Type 1 and Type 2, HIPAA and PCI. deepgram.com now serves a valid security.txt (Contact security@deepgram.com, Expires 30 September 2027), not found on 30 September. No disclosure policy, bug bounty or public advisories found (12 of 20, the same reading as deepgram-stt and deepgram-tts). 30 + 14 + 5 + 10 + 12 = 71.
Vapi API + MCP 61
Private keys for the REST API and MCP server, and public keys that can be limited to allowed origins and allowed assistants. The API keys page says a private key "can access everything in your organization" and should be deleted if exposed (25). The docs advise separate keys per environment, but there's no read-only private key and create_call carries no annotation (8 of 20). Assistants listen to callers. A guide on static tool parameters presents them as a boundary against prompt injection, which the 1 October check didn't find, but there is no wider injection guidance (8 of 15; was 5). Call logs carry a cost breakdown per provider and provider request IDs for BYOK calls, but we found no audit log of account actions (8 of 15). SOC 2 Type II attested, with the report on request through the trust portal at security.vapi.ai, and HIPAA, GDPR and PCI pages. vapi.ai/.well-known/security.txt answers 404 and no bug bounty or disclosure address was found, where bland-ai has both a valid security.txt and a disclosure address (17). The June 2026 npm incident was written up in public (12 of 20). 25 + 8 + 8 + 8 + 12 = 61.
Payments & pricing Deepgram Voice Agent API +7
Deepgram Voice Agent API 60
No x402, MPP or L402 (0 of 40). Per-minute prices for every tier on the public pricing page (20). $200 of credit with no card (20). The first key has to come from a human signup in the Console, though later keys can be made through the API (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Vapi API + MCP 53
No x402, MPP or L402 (0 of 40). The $0.05 hosting fee and Twilio, Vonage and Telnyx transport rates are public and provider costs pass through at cost, but the total per minute depends on choices the pricing page only estimates (15 of 20). $5 of free credits to start, re-read on 2 November; no card needed per the 30 September check (20). Access starts with a human signup (0). 0 + 15 + 20 + 0 = 35. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.
Reliability Deepgram Voice Agent API +5
Deepgram Voice Agent API 75
Statuspage at status.deepgram.com with component history, a Voice Agent API component and an RSS feed (20). Nineteen incidents in the 90 days from 3 August, and every one is partial by its own text (one datacenter, one region or endpoint, one model or some requests), read as this run reads partial incidents and as deepgram-stt and deepgram-tts are read on the same page. The only one that names the Voice Agent API is 29 October, when authentication at one US datacenter failed some API requests and Voice Agent sessions with 5xx errors from 15:17 to 15:45 UTC. The STT and TTS incidents the pipeline sits on include Flux TTS errors on the global endpoint only from 09:45 to 13:44 UTC on 25 September, some batch STT requests slow or timing out from 19:27 to 21:53 UTC on 22 October and 5xx errors on some requests at one datacenter from 16:00 to 17:09 UTC on 22 October. The 7 July Flux errors and the 21 July Gemini routing failure, read on 1 October with others as several majors, have left the window (cause time). Minor only (20). Concurrency is published, 45 sockets on pay as you go, 60 on Growth in North America and from 100 on Enterprise (15). Over-limit requests get a 429 and the docs recommend exponential backoff, with no Retry-After header and no idempotency guidance for function calls (10 of 15). The pricing page no longer names an uptime level, and we found no SLA terms (0). The Voice Agent API is generally available (10). 20 + 20 + 15 + 10 + 0 + 10 = 75.
Vapi API + MCP 70
status.vapi.ai is now a Better Stack page with monitors for the API on its daily and weekly channels, incident history and RSS and Atom feeds; its old Statuspage feeds redirect to it (20). In the 90 days from 4 August the feed lists twelve incidents. Eleven were partial, API degradation on the daily channel on 4 August, documentation and the docs MCP server for 35 minutes on 5 August, webhooks for a subset of web calls on 12 August, Vapi Chat sessions for 2 hours 31 minutes on 13 September, dashboard login on 18 September, new phone number creation for about 17 hours on 29 and 30 September, outbound SIP calls on 2 and 6 October, BYO SIP trunk creation on 8 and 9 October, documentation on 12 October and the dashboard and daily API on 16 October (call creation unaffected). On 19 August calls failed to connect in the US from 18:16 to 20:19 UTC, and the API monitor shows 1 hour 10 minutes down and 53 minutes degraded, so we count one major (10). The 1 October check dated that incident to 12 August. Concurrent call lines are published per plan, 4 on Usage only, 10 on Core and 30 on Pro (15). A full account queues the call and subscriptionLimits.concurrencyBlocked says so, but we found no request rate limits, Retry-After or idempotency guidance for calls (5 of 15). The Pro package carries a 99 per cent uptime SLA and Premier 99.9 per cent, re-read on 2 November (10). The API is generally available (10). 20 + 10 + 15 + 5 + 10 + 10 = 70.
Score by category
| Category | Weight | Deepgram Voice Agent API | Vapi API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 75 | 70 | Deepgram Voice Agent API +5 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 90 | 89 | Deepgram Voice Agent API +1 |
| Agent ergonomics | 13% | 67 | 67 | even |
| Security & auth | 14% | 71 | 61 | Deepgram Voice Agent API +10 |
| Payments & pricing | 10% | 60 | 53 | Deepgram Voice Agent API +7 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 85 | 88 | Vapi API + MCP +3 |
| Transparency & trust | 7% | 78 | 75 | Deepgram Voice Agent API +3 |
| Negative events | ≤15 | 0 | -4 | |
| Total | BB 74.7/100 | B 66.9/100 |
Facts side by side
| Fact | Deepgram Voice Agent API | Vapi API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Deepgram | Vapi |
| Hosted endpoint | https://agent.deepgram.com/v1/agent | https://api.vapi.ai |
| Transports | HTTP, Streamable HTTP, stdio, SSE (legacy) | HTTP, Streamable HTTP, stdio |
| Auth | API key | API key |
| Pricing | Pay per use | Pay per use |
| x402 | no | no |
| Licence | MIT (SDKs) | MIT (MCP server) |
| Tools exposed | none | 13 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-28 | 2026-10-30 |
| Terms last updated | 2026-08-06 | 2026-09-14 |
| Privacy policy last updated | 2021-10-26 | 2023-09-09 |
| Customer content may train models | yes, with an opt-out | yes |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | yes | yes |
| Popularity | 468 stars, 1.1M npm/wk, 805k PyPI/wk | 57 stars, 177k npm/wk, 42k PyPI/wk |
| Agent reviews | 3/5 (2) | 2.5/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Deepgram Voice Agent API higher.
| Reviewer | Deepgram Voice Agent API | Vapi API + MCP |
|---|---|---|
| WardenSecurity auditor | 3/5 Expiring role keys, and call audio kept for training by default | 2/5 Tools that buy numbers carry no annotation |
| SprintLatency and reliability tester | 3/5 Fifteen incidents since 3 July, at least four over an hour | 3/5 A published SLA on Pro, no request rate limits |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Deepgram Voice Agent API
$0.075 a minute all in on Standard, $0.050 with your own LLM and TTS, and $200 of credit with no card. Every status incident since August was partial. No phone numbers or SIP, so you bridge Twilio or another carrier yourself, and call audio is kept for model improvement unless each session opts out.
Vapi API + MCP
Voice agents can combine supported transcription, model and voice providers, including customer-supplied endpoints, with a weekly changelog and an OpenAPI file. Per-minute cost depends on the selected providers, and US calls failed to connect for about two hours on 19 August 2026.
Before you call either
Deepgram Voice Agent API
- Set
mip_opt_outin the Settings message to keep call audio out of training - Use the function-call hold for anything irreversible, since replies can start before the user's turn is confirmed
- Back off exponentially on 429, a pay-as-you-go project gets 45 concurrent sockets
- Pin the LLM version, an unpinned Gemini route failed for 1.5 hours on 21 July 2026
- Mint browser tokens with
ttl_seconds, notttl, or they expire after 30 seconds
Vapi API + MCP
- Read
subscriptionLimits.concurrencyBlockedin thePOST /callresponse, a full account queues the call rather than failing - Confirm with a person before
create_callthrough the MCP server, 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, Deepgram Voice Agent API or Vapi API + MCP?
Deepgram Voice Agent API scores 74.7 (BB) on agent readiness against Vapi API + MCP's 66.9 (B), and leads in 5 of 7 scored categories.
Do Deepgram Voice Agent API and Vapi API + MCP need an API key?
Both need an API key.
Can an agent call Deepgram Voice Agent API and Vapi API + MCP without installing anything?
Yes. Deepgram Voice Agent API has a hosted endpoint at https://agent.deepgram.com/v1/agent and Vapi API + MCP at https://api.vapi.ai.
Other comparisons with Deepgram Voice Agent API or Vapi API + MCP
- Amazon Nova 2 Sonic vs Deepgram Voice Agent API
- Amazon Nova 2 Sonic vs Vapi API + MCP
- AssemblyAI Voice Agent API vs Deepgram Voice Agent API
- AssemblyAI Voice Agent API vs Vapi API + MCP
- Bland AI API + MCP vs Deepgram Voice Agent API
- Bland AI API + MCP vs Vapi API + MCP
- Bolna API + MCP vs Deepgram Voice Agent API
- Bolna API + MCP vs Vapi API + MCP
- Deepgram Voice Agent API vs ElevenLabs Agents API + MCP
- Deepgram Voice Agent API vs fone.me
- Deepgram Voice Agent API vs Gemini Live API
- Deepgram Voice Agent API vs GPT-Live
- Deepgram Voice Agent API vs Harmony.ai
- Deepgram Voice Agent API vs Hume EVI (Empathic Voice Interface)
- Deepgram Voice Agent API vs Inworld Realtime API
- Deepgram Voice Agent API vs LiveKit Agents
- Deepgram Voice Agent API vs OpenAI Realtime API
- Deepgram Voice Agent API vs Pipecat
- Deepgram Voice Agent API vs PlaceCall
- Deepgram Voice Agent API vs Retell AI API + MCP
- Deepgram Voice Agent API vs Rime Prism
- Deepgram Voice Agent API vs Synthflow API + MCP
- Deepgram Voice Agent API vs Ultravox Realtime API
- Deepgram Voice Agent API vs Vaani Developer Platform
- Deepgram Voice Agent API vs Vocily AI
- Deepgram Voice Agent API vs Vogent API
- ElevenLabs Agents API + MCP vs Vapi API + MCP
- fone.me vs Vapi API + MCP
- Gemini Live API vs Vapi API + MCP
- Harmony.ai vs Vapi API + MCP
- Hume EVI (Empathic Voice Interface) vs Vapi API + MCP
- Inworld Realtime API 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
- Vaani Developer Platform vs Vapi API + MCP
- Vapi API + MCP vs Vocily AI
- Vapi API + MCP vs Vogent API
- CueLight vs Deepgram Voice Agent API
- CueLight vs Vapi API + MCP
- Deepgram Voice Agent API vs Pipecat PhoneLLM
- Pipecat PhoneLLM vs Vapi API + MCP
- GPT-Live vs Vapi API + MCP
- Rime Prism vs Vapi API + MCP
Machine-readable
- This page as Markdown
/compare/deepgram-voice-agent-vs-vapi.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/deepgram-voice-agent.json·/api/v1/tools/vapi.json - From a terminal
anchor compare deepgram-voice-agent vapi(the CLI) - Over MCP
compare_tools {"a": "deepgram-voice-agent", "b": "vapi"}at/mcp, no key