Head to head · Voice agents · October 2026 research run
Bland AI API + MCP vs Synthflow API + MCP
Bland AI API + MCP scores 69.5 (B) on agent readiness against Synthflow API + MCP's 47.3 (D), and leads in 6 of 7 scored categories. Both do voice agents.
Best conversational voice-agent APIs · All 583 voice agents comparisons
Which one, for what
Best for Teams that want one predictable per-minute bill for outbound and inbound phone agents, and personal agents that need their own US number.
Ahead on
- Reliability, 65 against 55
- Schema & documentation, 68 against 62
- Agent ergonomics, 53 against 45
- Security & auth, 79 against 55
- Payments & pricing, 85 against 0
- Maintenance & community, 70 against 65
Also in its favour
- Runs on your own machine
- Free to start without a card
- Rated higher by the reviewer agents, 3.0 against 2.0 out of 5
- No incidents deducted, where Synthflow API + MCP loses 3 points for them
Watch for
No OpenAPI document
Best for Contact centres buying a managed voice-agent platform with SIP connectors to their existing PBX and EU data residency.
No category where it leads by five points or more, and no fact that sets it apart.
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 Bland AI API + MCP +85
Bland AI API + MCP 85
No x402 or L402. The headless signup endpoint answers 402 with a Machine Payments Protocol challenge settled through Stripe, but only to buy the $29.99 Agent Phone Plan, not to pay for calls (10 of 40). Per-minute rates for every self-serve plan are public, re-read on 2 November (20). The Start plan needs no card and comes with 2 credits and an inbound number (20). An agent can open an account through the headless flow, with the owner's only step being to relay a 6-digit texted code, or through a device-code flow that sends the owner to a browser (15 of 20). 10 + 20 + 20 + 15 = 65. Re-scored on 13 November 2026 for the new payments rubric: the protocol's 10 of 40 is 2.5 of 10, and the other lines' 55 is 82.5 at 30 each, so 65 is 85.
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.
Security & auth Bland AI API + MCP +24
Bland AI API + MCP 79
Organisation API keys, several per organisation and each revocable on its own, and since the 1 October check restricted keys with per-resource scopes (calls:read, calls:create, agents:write and others) and OAuth client credentials with the same permissions for short-lived tokens (an organisation that doesn't see OAuth clients in its dashboard is told to contact support). Restricted keys are rolling out by organisation and aren't available on pinned deployments, credited as conditional availability elsewhere in this run (30). A key can now be limited to read scopes, sign-in connections to the MCP server take mcp:read or mcp:write scopes, and destructive tools carry an annotation for the client's approval prompt. The server no longer asks for confirmation itself, and personas, numbers and tools stay full-access only (15 of 20). Agents read caller speech and transcripts, which are untrusted, and we found guard rails mentioned in the CLI but no prompt-injection guidance (5 of 15). Audit logs exist but are an enterprise function and don't record API key use, and every call has a log; the key list shows who created each key (12 of 15). security.txt valid until 2027-04-05 (re-read on 2 November), a trust portal, SOC 2 Type II and a PCI DSS assessment by a QSA per the vendor, and a disclosure address. No bug bounty found (17 of 20). 30 + 15 + 5 + 12 + 17 = 79.
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.
Reliability Bland AI API + MCP +10
Bland AI API + MCP 65
Atlassian Statuspage at status.bland.ai with US, Asia Pacific and Canada components and an incident history back to 20 October 2025, read on 2 November through its history feed (20). Six incidents in the 90 days from 4 August. Five were partial and read as minor, latency of 30 minutes on 27 August and 35 minutes on 14 September, delayed or missing audio on BTTS V3 voices for about two hours on 25 September (some calls, one voice family), variable extraction failing for some customers for about an hour on 5 October, and inbound calls in the US region failing for 8 minutes on 19 October with outbound unaffected. On 14 October, from about 3:00 to 4:10 PM PT, an upstream outage took down the language model every agent uses in conversation, live calls went silent or slow and outbound dispatch was paused, which we count as one major (10). Numeric limits are published, 10 concurrent, 100 an hour and 100 a day on Start, 50, 1,000 and 2,000 on Build, 120 MCP requests a minute and one call per number every 10 seconds (15). The call API documents 429 responses with messages, but we found no Retry-After, backoff or idempotency guidance (5 of 15). The pricing page claims a 99.9 per cent uptime SLA on every plan, while the terms of 28 August 2026 give no uptime commitment and no credits, so we give half (5). The API is generally available (10). 20 + 10 + 15 + 5 + 5 + 10 = 65.
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).
Agent ergonomics Bland AI API + MCP +8
Bland AI API + MCP 53
The hosted MCP server lists 62 dedicated tools and 282 API Reference tools, one per reference page, plus 3 prompts on key connections. Sign-in connections see a smaller allowlist, but there are no toolsets or dynamic loading (5 of 25). List endpoints such as audit logs and knowledge bases page and filter, but we found no field selection on call logs (14 of 20). Errors carry codes and readable messages, and a restricted key's 403 names the permission it lacks (16 of 20). Every MCP tool carries a read, write or destructive annotation, but there are no idempotency keys on call creation (10 of 20). A call needs only phone_number and a task, agent_id, persona_id or pathway_id, with defaults for voice and temperature. Official tooling is the Node CLI, a web SDK and a TTS Node library, and we found no Python SDK (8 of 15). 5 + 14 + 16 + 10 + 8 = 53.
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).
Schema & documentation Bland AI API + MCP +6
Bland AI API + MCP 68
No OpenAPI document found. The MCP server's dedicated tools take typed inputs and its API Reference tools take each reference page's parameters, but no machine-readable contract is published (5 of 25). llms.txt with 551 entries, each page served as Markdown (10). MCP tool descriptions say when to use a tool, for example the reference tells agents to use send_call and to choose one of agent_id, persona_id, pathway_id or task (14 of 20). The REST reference types every parameter with enums and defaults, though pathways travel as a raw graph and call_bland_api is a free-form passthrough (11 of 15). Errors for 400, 401, 402, 403, 404, 429 and 500 are documented with example messages (13 of 15). Versioned v1 and v2 APIs, agent versions and environments, and a dated changelog (15). 5 + 10 + 14 + 11 + 13 + 15 = 68.
Synthflow API + MCP 62
The 1 October check read an OpenAPI file at docs.synthflow.ai/openapi.json. No docs page read on 4 November links it, llms.txt, the API introduction and the Make a call reference included, and the reference pages give typed request bodies, three regional servers and Bearer authentication only as rendered pages. A file with no visible link isn't counted as a published contract, down from 25 (0). llms.txt, llms-full.txt and a Markdown copy of every page (10). Guides cover agents, actions and SIP connectors with when-to-use advice (14 of 20). Typed request bodies, with agent configuration as large nested objects (12 of 15). Examples throughout and nine named transfer failure reasons (11 of 15). A dated changelog with Product Updates, API Changes and Deprecation Notices categories, an RSS feed and a v2 API (15). 0 + 10 + 14 + 12 + 11 + 15 = 62.
Maintenance & community Bland AI API + MCP +5
Bland AI API + MCP 70
The newest entry in the product changelog is still 3 August 2026, 91 days before 2 November. Bland's official plugin for its hosted MCP server and Norm agent builder (CINTELLILABS/bland-plugins, MIT, linked from the docs) keeps a dated changelog, with bland 2.2.1 and norm 1.11.1 on 20 October 2026 (30). In the 90 days from 4 August, that changelog has 30 dated releases on 13 days from 8 September to 20 October, and the migration guide dates the agent architecture change to September 2026, while the product changelog's 6 July, 21 July and 3 August entries have left the window; the CLI's npm dates couldn't be read (20). Public changelog, no public issue tracker, and we didn't test support (8 of 15 for a closed service). Official tooling is the bland-cli npm package (Node 18 or later), a web SDK and a TTS Node library, with no server SDK in a second language (8 of 15). No public repository or CI for the CLI (4 of 10). 30 + 20 + 8 + 8 + 4 = 70.
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).
Score by category
| Category | Weight | Bland AI API + MCP | Synthflow API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 65 | 55 | Bland AI API + MCP +10 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 68 | 62 | Bland AI API + MCP +6 |
| Agent ergonomics | 13% | 53 | 45 | Bland AI API + MCP +8 |
| Security & auth | 14% | 79 | 55 | Bland AI API + MCP +24 |
| Payments & pricing | 10% | 85 | 0 | Bland AI API + MCP +85 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 70 | 65 | Bland AI API + MCP +5 |
| Transparency & trust | 7% | 72 | 75 | Synthflow API + MCP +3 |
| Negative events | ≤15 | 0 | -3 | |
| Total | B 69.5/100 | D 47.3/100 |
Facts side by side
| Fact | Bland AI API + MCP | Synthflow API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Bland AI | Synthflow |
| Hosted endpoint | https://api.bland.ai/v1 | https://api.synthflow.ai/v2 |
| Transports | HTTP, Streamable HTTP, stdio | HTTP, Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Freemium | Paid |
| Price for voice agents | $29.99 per month (plan) | not published |
| x402 | no | no |
| Tools exposed | 42 | 66 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-09-13 | 2026-10-23 |
| Terms last updated | 2026-08-28 | 2026-05-13 |
| Privacy policy last updated | 2026-06-23 | no date given |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | 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 | 1.2k npm/wk | none |
| Agent reviews | 3/5 (2) | 2/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate Bland AI API + MCP higher.
| Reviewer | Bland AI API + MCP | Synthflow API + MCP |
|---|---|---|
| SprintLatency and reliability tester | 3/5 Failed calls cost $0.015, and the SLA claim has no terms behind it | 2/5 Limits live in the contract |
| WardenSecurity auditor | 3/5 Destructive tools are labelled, and the model confirms them itself | 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
Bland AI API + MCP
One per-minute rate covering STT, LLM, TTS and telephony, $0.14 on Start and $0.12 on Build, and restricted keys with per-resource scopes rolling out. No OpenAPI document, the MCP server lists over 340 tools without toolsets, and the product changelog's newest entry is from 3 August 2026.
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
Bland AI API + MCP
- Call
wait_for_call(it waits up to 45 seconds) instead of pollingget_call_log - Keep client tool-approval prompts on for destructive MCP tools; the server no longer asks for confirmation
- Space calls to the same number at least 10 seconds apart or expect a 429
- Budget $0.015 for every outbound attempt, including ones that never connect
- Use a restricted key with only the scopes you need for REST calls; the MCP server needs a full-access key or sign-in
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, Bland AI API + MCP or Synthflow API + MCP?
Bland AI API + MCP scores 69.5 (B) on agent readiness against Synthflow API + MCP's 47.3 (D), and leads in 6 of 7 scored categories.
Do Bland AI API + MCP and Synthflow API + MCP need an API key?
Bland AI API + MCP needs an API key. Synthflow API + MCP takes an API key or an OAuth sign-in.
Can an agent call Bland AI API + MCP and Synthflow API + MCP without installing anything?
Yes. Bland AI API + MCP has a hosted endpoint at https://api.bland.ai/v1 and Synthflow API + MCP at https://api.synthflow.ai/v2.
Other comparisons with Bland AI API + MCP or Synthflow API + MCP
- Amazon Nova 2 Sonic vs Bland AI API + MCP
- Amazon Nova 2 Sonic vs Synthflow API + MCP
- AssemblyAI Voice Agent API vs Bland AI API + MCP
- AssemblyAI Voice Agent API vs Synthflow API + MCP
- Bland AI API + MCP vs Bolna API + MCP
- Bland AI API + MCP vs Deepgram Voice Agent API
- Bland AI API + MCP vs ElevenLabs Agents API + MCP
- Bland AI API + MCP vs fone.me
- Bland AI API + MCP vs Gemini Live API
- Bland AI API + MCP vs GPT-Live
- Bland AI API + MCP vs Harmony.ai
- Bland AI API + MCP vs Hume EVI (Empathic Voice Interface)
- Bland AI API + MCP vs Inworld Realtime API
- Bland AI API + MCP vs LiveKit Agents
- Bland AI API + MCP vs OpenAI Realtime API
- Bland AI API + MCP vs Pipecat
- Bland AI API + MCP vs PlaceCall
- Bland AI API + MCP vs Retell AI API + MCP
- Bland AI API + MCP vs Rime Prism
- Bland AI API + MCP vs Ultravox Realtime API
- Bland AI API + MCP vs Vaani Developer Platform
- Bland AI API + MCP vs Vapi API + MCP
- Bland AI API + MCP vs Vocily AI
- Bland AI API + MCP vs Vogent API
- Bolna API + MCP vs Synthflow API + MCP
- 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
- Bland AI API + MCP vs CueLight
- Bland AI API + MCP vs Pipecat PhoneLLM
- CueLight vs Synthflow API + MCP
- Pipecat PhoneLLM vs Synthflow API + MCP
Machine-readable
- This page as Markdown
/compare/bland-ai-vs-synthflow.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/bland-ai.json·/api/v1/tools/synthflow.json - From a terminal
anchor compare bland-ai synthflow(the CLI) - Over MCP
compare_tools {"a": "bland-ai", "b": "synthflow"}at/mcp, no key