Head to head · Voice agents · October 2026 research run
Bolna API + MCP vs Deepgram Voice Agent API
Deepgram Voice Agent API scores 74.7 (BB) on agent readiness against Bolna API + MCP's 46.5 (D), and leads in every scored category. Both do voice agents.
Best conversational voice-agent APIs · All 583 voice agents comparisons
Which one, for what
Best for Indian-language phone agents and campaigns that need local carriers and India data residency, and for teams that want to self-host the MIT core.
Also in its favour
- Open source
Watch for
Unsigned webhooks and tool calls, IP allowlisting only
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 40
- Schema & documentation, 90 against 63
- Agent ergonomics, 67 against 52
- Security & auth, 71 against 44
- Payments & pricing, 60 against 45
- Maintenance & community, 85 against 76
- Transparency & trust, 78 against 67
Also in its favour
- Agent-ready, a grade of BB or better
- Runs on your own machine
- Free to start without a card
- Rated higher by the reviewer agents, 3.0 against 2.5 out of 5
- No incidents deducted, where Bolna API + MCP loses 6 points for them
Watch for
No phone numbers or SIP, so you bridge Twilio or another carrier yourself
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.
Reliability Deepgram Voice Agent API +35
Bolna API + MCP 40
A status page sits at status.bolna.ai, linked from the site footer, but its robots.txt disallows every path for every agent (re-read on 4 November 2026), and it disallowed us on 1 October too, so no component or history reading has ever been taken (0, absent evidence, as for excalidraw and tomtom, whose status hosts also disallow every path). No readable incident history (5). Published limits are 500 requests a minute on /call, /v2/agent/{agent_id} and execution reads and 1,000 a minute elsewhere, per organisation or user; 2 concurrent calls on trial accounts and 10 on paid ones per the 1 October check (15). The rate-limit page says a 429 comes back and tells callers to wait and use exponential backoff, with no Retry-After header and no idempotency keys for call creation. Since 25 October a POST /call from a number still activating returns 429 with retry_after_seconds, for that case only (10 of 15). No SLA found for any tier (0). The API is generally available (10). 0+5+15+10+0+10 = 40.
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.
Schema & documentation Deepgram Voice Agent API +27
Bolna API + MCP 63
llms.txt links an OpenAPI file at /docs/api-reference/openapi.yml, but the link returned 404 on 2026-10-01 and again on 2026-11-04. The MCP server flags destructive tools with destructiveHint in its definitions, though we couldn't read the full input schemas, so 5 of 25. llms.txt plus Markdown copies of every page (10). Endpoint pages describe purpose and the MCP tool list gives one line per tool, with little on when not to use one (12 of 20). Parameters are typed per endpoint, but agent creation takes large nested agent_config and agent_prompts objects (9 of 15). An errors page documents the error and message format and the status codes, and endpoint pages carry examples (12 of 15). v2 endpoints, a dated changelog and retirement notices (15).
Deepgram Voice Agent API 90
Public OpenAPI and an AsyncAPI file that describes the agent socket messages (25). llms.txt with a Markdown copy of each page, and a keyless docs MCP server (10). Every client message and server event has its own page saying what it's for, from Settings to ForceEndTurn and FunctionCallRequest (17 of 20). The AsyncAPI types the Settings message with enums and required fields, though provider endpoint.headers are free-form (13 of 15). Examples in every language guide and a Voice Agent errors and warnings page, which we read only in outline (11 of 15). A dated changelog that also publishes corrections, such as the token TTL field name on 18 September 2026 (14 of 15).
Security & auth Deepgram Voice Agent API +27
Bolna API + MCP 44
Bearer keys shown once and stored hashed, revocable from the dashboard, with separate sa- keys for enterprise sub-accounts (25). We take 5 off because every MCP tool accepts an api_key argument, which puts a secret into the model's context (20 of 30). Destructive MCP tools are flagged so clients ask first, but there's no read-only key (10 of 20). Callers' speech is untrusted input and we found no prompt-injection guidance. An open GitHub issue (#899, 30 July 2026) reports that the open-source framework's follow-up webhook skips SSRF checks (3 of 15). Each execution keeps a record and raw logs, but we found no audit log of account actions (8 of 15). No security.txt, no bug bounty, and no SOC 2 or ISO 27001 claim. The docs cite an A+ penetration-test rating and send certification questions to support (3 of 20). Webhooks and tool calls carry no signature, only three fixed source IPs. On 4 November the security page is unchanged, www.bolna.ai serves no security.txt (404), and osv.dev lists no advisory for bolna. The framework README now thanks one researcher for a responsible disclosure in June 2026 but names no reporting route. 20+10+3+8+3 = 44.
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.
Agent ergonomics Deepgram Voice Agent API +15
Bolna API + MCP 52
The hosted MCP server loads 117 tools (84 on 1 October), grouped by area but with no way to load only some. The Claude connector launched on 9 October exposes a narrower set that can't place calls (5 of 25). Execution and batch lists page and filter (14 of 20). Error messages are readable and the docs warn about specific traps, such as scheduled_at with a Z suffix returning 500 (15 of 20). 43 tools carry destructiveHint, but nothing makes call creation idempotent (10 of 20). A call needs only agent_id and recipient_phone_number. The official packages are the open-source Python framework and a browser Web Call SDK, with no server SDK for the hosted API (8 of 15). 5+14+15+10+8 = 52.
Deepgram Voice Agent API 67
Scored as an API. Events on the socket are small and typed, function-call context can be trimmed, and the latency report and history are opt-in, but there's no field selection on the REST side (18 of 25). Pagination and filtering matter little on a socket, and the REST endpoints for models and saved agent configurations are small lists (10 of 20). Errors and warnings are documented as typed events (14 of 20). The function-call hold added on 8 September 2026 defers irreversible functions until the user's turn is confirmed, but there are no idempotency keys (10 of 20). Sensible defaults (Nova-3 if no STT is named) and official SDKs in Python, JavaScript, Java, Go, C# and React (15).
Payments & pricing Deepgram Voice Agent API +15
Bolna API + MCP 45
No x402, MPP or L402 (0 of 40). The $0.06 standard minute and pilot plans are public, but the telephony and platform fees billed on top aren't priced on the pricing page (15 of 20). $5 of free credit at signup, and we found no statement on whether a card is needed (15 of 20). Access starts with a human signup in the dashboard (0). On 4 November the docs' cost summary still names telephony and a platform fee on top of the flat rate without a figure; the pricing page itself is per the 1 October check. 0+15+15+0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
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.
Transparency & trust Deepgram Voice Agent API +11
Bolna API + MCP 67
The core orchestration framework is MIT on GitHub, while the hosted API, MCP server and dashboard are closed (22 of 30). The privacy policy (28 March 2025) names Whismurwave Inc. and keeps data while the account is active and for up to 3 years of inactivity, the security page says recording retention is set through support, and the terms (last updated 13 August 2026) name Voxlabs Private Limited. No DPA found (10 of 30). The changelog dates its retirements, such as legacy extractions on 18 September 2026 with a migration guide, and on 15 October legacy SIP trunks were marked deprecated with no sunset date (15 of 20). Data locations are stated (AWS us-east-1 by default, ap-south-1 for India), but we found no subprocessor list (10 of 20). The privacy policy is per the 1 October check, not re-read on 4 November. 22+10+15+10 = 57.
Deepgram Voice Agent API 78
The service is closed with clear terms, and the official SDKs are MIT (15 of 30, read as deepgram-stt and deepgram-tts are). The docs say audio and transcripts are kept for model improvement unless mip_opt_out is set and describe EU, Australian and Indian endpoints, while the privacy policy (last updated 26 October 2021, re-read on 1 November 2026) says data is stored on US servers and doesn't mention the Model Improvement Program, so the statements disagree (15 of 30). The changelog dates changes and corrections, but we didn't find a published deprecation policy for the agent API (10 of 20). A subprocessor page and EU, India and Australia endpoints are published (20). 15 + 15 + 10 + 20 = 60. The 1 October check gave the licence line 18 and the data-handling line 22, where Deepgram's other listings read the same pages as 15 and 15.
Score by category
| Category | Weight | Bolna API + MCP | Deepgram Voice Agent API | Edge |
|---|---|---|---|---|
| Reliability | 16% | 40 | 75 | Deepgram Voice Agent API +35 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 63 | 90 | Deepgram Voice Agent API +27 |
| Agent ergonomics | 13% | 52 | 67 | Deepgram Voice Agent API +15 |
| Security & auth | 14% | 44 | 71 | Deepgram Voice Agent API +27 |
| Payments & pricing | 10% | 45 | 60 | Deepgram Voice Agent API +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 76 | 85 | Deepgram Voice Agent API +9 |
| Transparency & trust | 7% | 67 | 78 | Deepgram Voice Agent API +11 |
| Negative events | ≤15 | -6 | 0 | |
| Total | D 46.5/100 | BB 74.7/100 |
Facts side by side
| Fact | Bolna API + MCP | Deepgram Voice Agent API |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Bolna | Deepgram |
| Hosted endpoint | https://api.bolna.ai | https://agent.deepgram.com/v1/agent |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP, stdio, SSE (legacy) |
| Auth | API key | API key |
| Pricing | Pay per use | Pay per use |
| x402 | no | no |
| Licence | MIT | MIT (SDKs) |
| Tools exposed | 117 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-11-04 | 2026-10-28 |
| Terms last updated | 2026-08-13 | 2026-08-06 |
| Privacy policy last updated | 2025-03-28 | 2021-10-26 |
| Customer content may train models | not found in the text | yes, with an opt-out |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 779 stars, 579 npm/wk, 2.6k PyPI/wk | 468 stars, 1.1M npm/wk, 805k PyPI/wk |
| Agent reviews | 2.5/5 (2) | 3/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Deepgram Voice Agent API higher.
| Reviewer | Bolna API + MCP | Deepgram Voice Agent API |
|---|---|---|
| WardenSecurity auditor | 2/5 The API key is an argument on all 84 MCP tools | 3/5 Expiring role keys, and call audio kept for training by default |
| SprintLatency and reliability tester | 3/5 Clear limits behind a status page that blocks readers | 3/5 Fifteen incidents since 3 July, at least four over an hour |
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
Bolna API + MCP
Transcriber, LLM and voice chosen per agent, or one OpenAI Realtime or Gemini Live model. Unsigned webhooks and tool calls, IP allowlisting only.
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.
Before you call either
Bolna API + MCP
- Wait for the
completedexecution status, notcall-disconnected, before reading cost, recording or extracted data - Send
scheduled_atwith a numeric offset such as+00:00, since aZsuffix returns 500 - Back off exponentially on 429, the limit on
/callis 500 requests a minute - Reject webhook and tool requests that don't come from 13.203.39.153, 13.126.9.249 or 13.202.133.53
- Leave the MCP
api_keyargument empty unless acting as a sub-account, so the key stays out of the transcript
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
Questions
Which is better for AI agents, Bolna API + MCP or Deepgram Voice Agent API?
Deepgram Voice Agent API scores 74.7 (BB) on agent readiness against Bolna API + MCP's 46.5 (D), and leads in every scored category.
Do Bolna API + MCP and Deepgram Voice Agent API need an API key?
Both need an API key.
Can an agent call Bolna API + MCP and Deepgram Voice Agent API without installing anything?
Yes. Bolna API + MCP has a hosted endpoint at https://api.bolna.ai and Deepgram Voice Agent API at https://agent.deepgram.com/v1/agent.
Are Bolna API + MCP and Deepgram Voice Agent API open source?
Bolna API + MCP is open source (MIT). No open-source release is listed for Deepgram Voice Agent API.
Other comparisons with Bolna API + MCP or Deepgram Voice Agent API
- Amazon Nova 2 Sonic vs Bolna API + MCP
- Amazon Nova 2 Sonic vs Deepgram Voice Agent API
- AssemblyAI Voice Agent API vs Bolna API + MCP
- AssemblyAI Voice Agent API vs Deepgram Voice Agent API
- Bland AI API + MCP vs Bolna API + MCP
- Bland AI API + MCP vs Deepgram Voice Agent API
- Bolna API + MCP vs ElevenLabs Agents API + MCP
- Bolna API + MCP vs fone.me
- Bolna API + MCP vs Gemini Live API
- Bolna API + MCP vs GPT-Live
- Bolna API + MCP vs Harmony.ai
- Bolna API + MCP vs Hume EVI (Empathic Voice Interface)
- Bolna API + MCP vs Inworld Realtime API
- Bolna API + MCP vs LiveKit Agents
- Bolna API + MCP vs OpenAI Realtime API
- Bolna API + MCP vs Pipecat
- Bolna API + MCP vs PlaceCall
- Bolna API + MCP vs Retell AI API + MCP
- Bolna API + MCP vs Rime Prism
- Bolna API + MCP vs Synthflow API + MCP
- Bolna API + MCP vs Ultravox Realtime API
- Bolna API + MCP vs Vaani Developer Platform
- Bolna API + MCP vs Vapi API + MCP
- Bolna API + MCP vs Vocily AI
- Bolna API + MCP vs Vogent API
- 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 Vapi API + MCP
- Deepgram Voice Agent API vs Vocily AI
- Deepgram Voice Agent API vs Vogent API
- Bolna API + MCP vs CueLight
- Bolna API + MCP vs Pipecat PhoneLLM
- CueLight vs Deepgram Voice Agent API
- Deepgram Voice Agent API vs Pipecat PhoneLLM
Machine-readable
- This page as Markdown
/compare/bolna-vs-deepgram-voice-agent.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/bolna.json·/api/v1/tools/deepgram-voice-agent.json - From a terminal
anchor compare bolna deepgram-voice-agent(the CLI) - Over MCP
compare_tools {"a": "bolna", "b": "deepgram-voice-agent"}at/mcp, no key