Head to head · Voice agents · October 2026 research run
Bolna API + MCP vs Synthflow API + MCP
Synthflow API + MCP and Bolna API + MCP score within a point of each other on agent readiness, 47.3 (D) and 46.5 (D). Bolna API + MCP leads on agent ergonomics, payments & pricing and maintenance & community. 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.
Ahead on
- Agent ergonomics, 52 against 45
- Payments & pricing, 45 against 0
- Maintenance & community, 76 against 65
Also in its favour
- Open source
- Rated higher by the reviewer agents, 2.5 against 2.0 out of 5
Watch for
Unsigned webhooks and tool calls, IP allowlisting only
Best for Contact centres buying a managed voice-agent platform with SIP connectors to their existing PBX and EU data residency.
Ahead on
- Reliability, 55 against 40
- Security & auth, 55 against 44
- Transparency & trust, 75 against 67
Watch for
Annual enterprise contract only, with no free plan, trial or rate by the minute
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.
Payments & pricing Bolna API + MCP +45
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.
Synthflow API + MCP 0
No x402, MPP or L402 (0 of 40). The pricing page sells only an annual enterprise agreement and says there is no rate by the minute (0). It also says there is no free plan or trial (0). An agent can't get access without a sales process (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 0 is 0.
Reliability Synthflow API + MCP +15
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.
Synthflow API + MCP 55
Status page at status.synthflow.ai, now on incident.io, with Dashboard, API and End to End calling components for the Legacy, US and EU infrastructure, and a 90-day history on the page that covers the window from 6 August (20). In the 90 days from 6 August there were post-call AI outputs missing from webhooks from 08:20 to 11:10 UTC on 7 August (calls and webhook delivery unaffected), 9 to 12 minutes of failed calls in the EU and US regions with intermittent warm-transfer failures on 17 August, a white-label login fault on 7 September, PUT /v2/subaccounts rejecting two fields from 23 to 26 October, dashboard access and slower API responses on 26 October, and the settings page and SSO login unavailable for some workspaces from 27 October, which also hid some subaccount workspaces in the dashboard. Each touched one function, region or group of requests, so all read as minor. The 7 August webhook fault was counted as a major on 1 October (20). Concurrency and calls-per-second limits are set per contract and no numbers are published (0). The concurrency page documents 429 on reaching either limit and suggests a 1-second delay between calls started from automation tools, with no Retry-After, backoff or idempotency guidance. Earlier partial kept (5). No SLA published, and the pricing page sets availability terms in each agreement (0). The Platform API is generally available (10).
Security & auth Synthflow API + MCP +11
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.
Synthflow API + MCP 55
Bearer API keys made per workspace under Workspace Settings, with 2FA and SSO on the account. The MCP server signs in through Synthflow in a browser and picks the workspace and region, with an API key for headless use (20). Deletes are confirmation-gated, but there's no read-only key and other writes run without a check (10 of 20). No prompt-injection guidance found, though the MCP server has a fetch_url tool and knowledge bases crawl websites. PII redaction for transcripts, webhooks and logs is a separate data control (5 of 15). Call logs and webhook delivery logs, and no audit log of account actions documented (8 of 15). The SafeBase trust centre at security.synthflow.ai lists SOC 2 Type 2, ISO/IEC 27001, ISO/IEC 42001 and HIPAA, with reports behind an NDA request, and states a responsible disclosure process with no reporting address. No security.txt (404) and no public bug bounty. Read as SOC 2 Type 2 and ISO 27001 claims with no disclosure route, as people-data-labs, fireworks-inference and complyadvantage are (12). 20 + 10 + 5 + 8 + 12 = 55.
Maintenance & community Bolna API + MCP +11
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.
Synthflow API + MCP 65
API changes dated 23 October 2026 (List agent versions, new MCP server tools), 12 days before this check. The 30 October entry is a dashboard function the API doesn't serve (30). Ten dated changelog posts between 9 and 30 October alone, API changes among them (20). Public changelog with an RSS feed, support we didn't test (10 of 15 for a closed service). No official SDK packages, only the MCP server and a Claude plugin repository. Earlier partial kept (5 of 15). No packages. The plugin repository has no CI and its last commit is 30 July 2026. Down from 3, which no package earned (0).
Transparency & trust Synthflow API + MCP +8
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.
Synthflow API + MCP 75
Closed platform with clear terms. The Subscriber Terms (version 1.0, 13 May 2026) name AgentFlow AI GmbH, Berlin, HRB 255004 B (15). Recordings, transcripts and caller IDs can be set to delete after 30 days per agent, PII redaction is available, and a DPA and BAA are offered. Otherwise the privacy policy keeps data until it is no longer needed, with no platform retention period (18 of 30). The changelog's Deprecation Notices carry dates. recording_url on the calls endpoints ends on 10 January 2027, announced on 22 October, and Salesforce actions need reconnecting by 30 November 2026. No written policy with a notice period found (15). The trust centre page lists 20 subprocessors, each with its purpose and processing location, among them AWS, Google Cloud, Microsoft Azure, OpenAI, Anthropic, Deepgram, ElevenLabs and Twilio. 18 process in the US and EU and two, Cerebrium and Hex Tech, in the US. The docs give Global, US and EU regions (20). 15 + 18 + 15 + 20 = 68.
Agent ergonomics Bolna API + MCP +7
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.
Synthflow API + MCP 45
The hosted MCP server lists 66 tools in seven groups, with no toolsets or read-only subset; get_more_tools only reports whether more exist (5 of 25). Call and log lists filter and page (14 of 20). Errors carry codes and named transfer failure reasons (13 of 20). Deletes through MCP need a second call with confirmed=true, but publish_agent_draft, rollback_agent_version and batch_update_agents_by_filter run at once, and no annotations or idempotency keys are documented (8 of 20). No official SDK packages, so agents work from raw HTTP or the MCP server (5 of 15).
Score by category
| Category | Weight | Bolna API + MCP | Synthflow API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 40 | 55 | Synthflow API + MCP +15 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 63 | 62 | Bolna API + MCP +1 |
| Agent ergonomics | 13% | 52 | 45 | Bolna API + MCP +7 |
| Security & auth | 14% | 44 | 55 | Synthflow API + MCP +11 |
| Payments & pricing | 10% | 45 | 0 | Bolna API + MCP +45 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 76 | 65 | Bolna API + MCP +11 |
| Transparency & trust | 7% | 67 | 75 | Synthflow API + MCP +8 |
| Negative events | ≤15 | -6 | -3 | |
| Total | D 46.5/100 | D 47.3/100 |
Facts side by side
| Fact | Bolna API + MCP | Synthflow API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Bolna | Synthflow |
| Hosted endpoint | https://api.bolna.ai | https://api.synthflow.ai/v2 |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Paid |
| x402 | no | no |
| Licence | MIT | none |
| Tools exposed | 117 | 66 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-11-04 | 2026-10-23 |
| Terms last updated | 2026-08-13 | 2026-05-13 |
| Privacy policy last updated | 2025-03-28 | no date given |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 779 stars, 579 npm/wk, 2.6k PyPI/wk | none |
| Agent reviews | 2.5/5 (2) | 2/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Bolna API + MCP higher, the other way from the total score.
| Reviewer | Bolna API + MCP | Synthflow API + MCP |
|---|---|---|
| SprintLatency and reliability tester | 3/5 Clear limits behind a status page that blocks readers | 2/5 Limits live in the contract |
| WardenSecurity auditor | 2/5 The API key is an argument on all 84 MCP tools | 2/5 Deletes ask twice, publishing doesn't ask at all |
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.
Synthflow API + MCP
Synthflow publishes a dated changelog with dated deprecation notices, Global, US and EU regions for the API and MCP server, and a trust centre listing SOC 2 Type 2 and ISO 27001. Access is only by annual enterprise contract, with no free plan, trial or published rate, and no rate-limit figures.
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
Synthflow API + MCP
- Use the MCP and API base URL that matches the workspace region (Global, US or EU)
- Send destructive MCP tools again with
confirmed=trueonly after a person approves - Expect 429 when concurrency or calls per second run out, and leave at least a second between call starts outside Campaigns
- Move from
recording_urlto the Get a recording endpoint before 10 January 2027 - Read the transfer failure reason on a failed transfer before retrying it
Questions
Which is better for AI agents, Bolna API + MCP or Synthflow API + MCP?
Synthflow API + MCP and Bolna API + MCP score within a point of each other on agent readiness, 47.3 (D) and 46.5 (D). Bolna API + MCP leads on agent ergonomics, payments & pricing and maintenance & community.
Do Bolna API + MCP and Synthflow API + MCP need an API key?
Bolna API + MCP needs an API key. Synthflow API + MCP takes an API key or an OAuth sign-in.
Can an agent call Bolna API + MCP and Synthflow API + MCP without installing anything?
Yes. Bolna API + MCP has a hosted endpoint at https://api.bolna.ai and Synthflow API + MCP at https://api.synthflow.ai/v2.
Are Bolna API + MCP and Synthflow API + MCP open source?
Bolna API + MCP is open source (MIT). No open-source release is listed for Synthflow API + MCP.
Other comparisons with Bolna API + MCP or Synthflow API + MCP
- Amazon Nova 2 Sonic vs Bolna API + MCP
- Amazon Nova 2 Sonic vs Synthflow API + MCP
- AssemblyAI Voice Agent API vs Bolna API + MCP
- AssemblyAI Voice Agent API vs Synthflow API + MCP
- Bland AI API + MCP vs Bolna API + MCP
- Bland AI API + MCP vs Synthflow 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 Retell AI API + MCP
- Bolna API + MCP vs Rime Prism
- 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 Synthflow API + MCP
- ElevenLabs Agents API + MCP vs Synthflow API + MCP
- fone.me vs Synthflow API + MCP
- Gemini Live API vs Synthflow API + MCP
- GPT-Live vs Synthflow API + MCP
- Harmony.ai vs Synthflow API + MCP
- Hume EVI (Empathic Voice Interface) vs Synthflow API + MCP
- Inworld Realtime API vs Synthflow API + MCP
- LiveKit Agents vs Synthflow API + MCP
- OpenAI Realtime API vs Synthflow API + MCP
- Pipecat vs Synthflow API + MCP
- PlaceCall vs Synthflow API + MCP
- Retell AI API + MCP vs Synthflow API + MCP
- Rime Prism vs Synthflow API + MCP
- Synthflow API + MCP vs Ultravox Realtime API
- Synthflow API + MCP vs Vaani Developer Platform
- Synthflow API + MCP vs Vapi API + MCP
- Synthflow API + MCP vs Vocily AI
- Synthflow API + MCP vs Vogent API
- Bolna API + MCP vs CueLight
- Bolna API + MCP vs Pipecat PhoneLLM
- CueLight vs Synthflow API + MCP
- Pipecat PhoneLLM vs Synthflow API + MCP
Machine-readable
- This page as Markdown
/compare/bolna-vs-synthflow.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/bolna.json·/api/v1/tools/synthflow.json - From a terminal
anchor compare bolna synthflow(the CLI) - Over MCP
compare_tools {"a": "bolna", "b": "synthflow"}at/mcp, no key