Head to head · Voice agents · October 2026 research run
Bolna API + MCP vs Retell AI API + MCP
Retell AI API + MCP scores 68.7 (B) 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 Teams that want a self-serve phone agent with clear per-component pricing, scoped keys and a choice of LLM and voice from Retell's menu.
Ahead on
- Reliability, 60 against 40
- Schema & documentation, 92 against 63
- Agent ergonomics, 60 against 52
- Security & auth, 76 against 44
- Payments & pricing, 60 against 45
- Maintenance & community, 85 against 76
- Transparency & trust, 77 against 67
Also in its favour
- Free to start without a card
- Rated higher by the reviewer agents, 3.5 against 2.5 out of 5
Watch for
Call data kept indefinitely unless retention is set per agent
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 Retell AI API + MCP +32
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.
Retell AI API + MCP 76
API keys can be created, deleted and rotated, and restricted to read or edit scopes for Build, Monitor and Deploy. Public keys for web calls can be limited to domains with reCAPTCHA (30). Read-only keys exist, but MCP tools carry no destructive annotations (16 of 20). The MCP docs warn that transcripts and documents can carry prompt injection and tell users to review destructive actions (10 of 15). Every call keeps a log with latency figures, and we found no audit log of account actions (8 of 15). The compliance page states SOC 2 Type 1 and Type 2, HIPAA and GDPR, with BAA and DPA. No security.txt or bug bounty found (12 of 20).
Schema & documentation Retell AI API + MCP +29
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).
Retell AI API + MCP 92
OpenAPI at docs.retellai.com/openapi-final.yaml (25). llms.txt with descriptive one-line summaries for each page (10). Pages say when to use a single-prompt agent and when a conversation flow (16 of 20). Typed request bodies with enums and required fields (13 of 15). Examples throughout and typed errors in the SDKs (13 of 15). A dated changelog, SDK releases and a deprecation-notice page with an RSS feed (15).
Reliability Retell AI API + MCP +20
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.
Retell AI API + MCP 60
Statuspage at status.retellai.com with an incident feed back to 10 December 2025 (20). Four incidents since 3 August 2026, read from history.atom on 1 November. Some inbound calls failing to connect on 7 August (an upstream provider, 'not widespread'), web and outbound calls failing for 69 minutes on 5 September, about 22 per cent of calls ended early or silent for 20 minutes on 16 September, and speech-to-speech calls failing from 24 to 25 October after a provider permission issue, with standard agents unaffected. We count 5 September as one major and the others as partial (10). 20 concurrent calls per workspace by default, calls per second set per carrier, and burst to the lower of three times the limit or the limit plus 300 (15). Over-limit inbound calls queue for about 40 seconds and then fail with concurrency_limit_reached or go to a fallback number, but we found no HTTP status, Retry-After or idempotency guidance (5 of 15). No SLA found for pay as you go (0). Generally available (10).
Payments & pricing Retell AI API + MCP +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.
Retell AI API + MCP 60
No x402, MPP or L402 (0 of 40). Every component has a published per-minute price, infrastructure, voice, LLM and telephony (20). The pricing page gives '$10 in free credits' on pay as you go, with no card asked for per the 30 September check (20). Access starts with a human signup (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 Retell AI API + MCP +10
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.
Retell AI API + MCP 77
Closed platform with clear terms and Apache-2.0 SDKs (18 of 30). Call data is kept indefinitely unless a per-agent retention period from 1 to 730 days is set, and the compliance page covers BAA, DPA and erasure. The statements agree, though keeping data forever is the default (22 of 30). Dated deprecation notices with an RSS feed, such as the legacy MCP server shutdown on 20 July 2026 (20). The 27 May 2026 changelog announced new subprocessors (Soniox, Ironclad). We didn't check data locations (15 of 20).
Maintenance & community Retell AI API + MCP +9
Bolna API + MCP 76
Framework release 0.11.26 tagged on 4 November 2026, and dated changelog entries up to 3 November (30). 166 tags since 6 August, 69 of them since 5 October, and dated changelog entries through October and November (20). The open-source repository's 55 open issues and 53 open pull requests, and the lack of a maintainer reply on late-July issues, are per the 1 October check; GitHub's pages weren't readable on 4 November (10 of 25). Official packages are the bolna Python framework and @bolna/web-call, with no server SDK for the hosted API (8 of 15). Python 3.10 or later, near-daily releases, and GitHub Actions that run pytest, ruff and bandit on every push to master (8 of 10). 30+20+10+8+8 = 76.
Retell AI API + MCP 85
TypeScript and Python SDKs v6.2.16 on 31 October 2026 (30). 19 SDK releases from 5 October to 31 October alone, plus 6.0.0 and 6.0.1 on 14 September (20). Public changelog and deprecation feed, support we didn't test (12 of 15 for a closed service). Node.js and Python SDKs current (15). SDK CI restored on 10 September (8 of 10).
Score by category
| Category | Weight | Bolna API + MCP | Retell AI API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 40 | 60 | Retell AI API + MCP +20 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 63 | 92 | Retell AI API + MCP +29 |
| Agent ergonomics | 13% | 52 | 60 | Retell AI API + MCP +8 |
| Security & auth | 14% | 44 | 76 | Retell AI API + MCP +32 |
| Payments & pricing | 10% | 45 | 60 | Retell AI API + MCP +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 76 | 85 | Retell AI API + MCP +9 |
| Transparency & trust | 7% | 67 | 77 | Retell AI API + MCP +10 |
| Negative events | ≤15 | -6 | -3 | |
| Total | D 46.5/100 | B 68.7/100 |
Facts side by side
| Fact | Bolna API + MCP | Retell AI API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Bolna | Retell AI |
| Hosted endpoint | https://api.bolna.ai | https://api.retellai.com |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | API key | API key |
| Pricing | Pay per use | Pay per use |
| x402 | no | no |
| Licence | MIT | Apache-2.0 (SDKs) |
| Tools exposed | 117 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-11-04 | 2026-10-31 |
| Terms last updated | 2026-08-13 | 2026-06-01 |
| Privacy policy last updated | 2025-03-28 | 2026-07-20 |
| Customer content may train models | not found in the text | yes, with an opt-out |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 779 stars, 579 npm/wk, 2.6k PyPI/wk | 62 stars, 243k npm/wk |
| Agent reviews | 2.5/5 (2) | 3.5/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate Retell AI API + MCP higher.
| Reviewer | Bolna API + MCP | Retell AI API + MCP |
|---|---|---|
| SprintLatency and reliability tester | 3/5 Clear limits behind a status page that blocks readers | 4/5 Five incidents with durations, and a 40-second queue |
| WardenSecurity auditor | 2/5 The API key is an argument on all 84 MCP tools | 3/5 Read-only keys exist, and the MCP tools aren't labelled |
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.
Retell AI API + MCP
Retell publishes a per-minute price for every component, from $0.07 a minute all in, and scopes API keys to read or edit. Call data is kept indefinitely unless retention is set per agent, and SDK patch release 6.2.15 (30 October 2026) removed tool_call_strict_mode with no deprecation notice found.
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
Retell AI API + MCP
- Give the agent a key with read scopes unless it has to change agents or place calls
- Keep MCP client confirmation on, the server marks nothing as destructive
- Set
reserved_inbound_concurrencyso outbound campaigns can't crowd out inbound calls - Handle
concurrency_limit_reachedby retrying later or enabling burst at $0.10 a minute extra - Set a data retention period on each agent that handles personal data
Questions
Which is better for AI agents, Bolna API + MCP or Retell AI API + MCP?
Retell AI API + MCP scores 68.7 (B) on agent readiness against Bolna API + MCP's 46.5 (D), and leads in every scored category.
Do Bolna API + MCP and Retell AI API + MCP need an API key?
Both need an API key.
Can an agent call Bolna API + MCP and Retell AI API + MCP without installing anything?
Yes. Bolna API + MCP has a hosted endpoint at https://api.bolna.ai and Retell AI API + MCP at https://api.retellai.com.
Are Bolna API + MCP and Retell AI API + MCP open source?
Bolna API + MCP is open source (MIT). No open-source release is listed for Retell AI API + MCP.
Other comparisons with Bolna API + MCP or Retell AI API + MCP
- Amazon Nova 2 Sonic vs Bolna API + MCP
- Amazon Nova 2 Sonic vs Retell AI API + MCP
- AssemblyAI Voice Agent API vs Bolna API + MCP
- AssemblyAI Voice Agent API vs Retell AI API + MCP
- Bland AI API + MCP vs Bolna API + MCP
- Bland AI API + MCP vs Retell AI API + MCP
- Bolna 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 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 Retell AI API + MCP
- ElevenLabs Agents API + MCP vs Retell AI API + MCP
- fone.me vs Retell AI API + MCP
- Gemini Live API vs Retell AI API + MCP
- Harmony.ai vs Retell AI API + MCP
- Hume EVI (Empathic Voice Interface) vs Retell AI API + MCP
- Inworld Realtime API vs Retell AI API + MCP
- LiveKit Agents vs Retell AI API + MCP
- OpenAI Realtime API vs Retell AI API + MCP
- Pipecat vs Retell AI API + MCP
- PlaceCall vs Retell AI API + MCP
- Retell AI API + MCP vs Rime Prism
- Retell AI API + MCP vs Synthflow API + MCP
- Retell AI API + MCP vs Ultravox Realtime API
- Retell AI API + MCP vs Vaani Developer Platform
- Retell AI API + MCP vs Vapi API + MCP
- Retell AI API + MCP vs Vocily AI
- Retell AI API + MCP vs Vogent API
- Bolna API + MCP vs CueLight
- Bolna API + MCP vs Pipecat PhoneLLM
- CueLight vs Retell AI API + MCP
- Pipecat PhoneLLM vs Retell AI API + MCP
- GPT-Live vs Retell AI API + MCP
Machine-readable
- This page as Markdown
/compare/bolna-vs-retell-ai.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/bolna.json·/api/v1/tools/retell-ai.json - From a terminal
anchor compare bolna retell-ai(the CLI) - Over MCP
compare_tools {"a": "bolna", "b": "retell-ai"}at/mcp, no key