Head to head · Voice agents · October 2026 research run
Bland AI API + MCP vs Bolna API + MCP
Bland AI API + MCP scores 69.5 (B) on agent readiness against Bolna API + MCP's 46.5 (D), and leads in 6 of 7 scored categories. Bolna API + MCP leads on maintenance & community. 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 40
- Schema & documentation, 68 against 63
- Security & auth, 79 against 44
- Payments & pricing, 85 against 45
- Transparency & trust, 72 against 67
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.5 out of 5
- No incidents deducted, where Bolna API + MCP loses 6 points for them
Watch for
No OpenAPI document
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
- Maintenance & community, 76 against 70
Also in its favour
- Open source
Watch for
Unsigned webhooks and tool calls, IP allowlisting only
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 +40
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.
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.
Security & auth Bland AI API + MCP +35
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.
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.
Reliability Bland AI API + MCP +25
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.
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.
Maintenance & community Bolna API + MCP +6
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.
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.
Schema & documentation Bland AI API + MCP +5
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.
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).
Transparency & trust Bland AI API + MCP +5
Bland AI API + MCP 72
Closed source with clear terms (15). The privacy policy (last updated 23 June 2026) keeps data 'as long as necessary' with no periods for recordings or transcripts, and the trust page says zero-retention processing is available. The terms and the privacy policy both name Intelliga Corporation, doing business as Bland AI (12 of 30). The December 2025 price change was announced with a date and transition credits, and the migration from pathways and personas to agents carries a 15 November 2026 deadline in the docs, but we found no deprecation policy (8 of 20). A subprocessor list of 17 entries with locations, updated 8 September 2026, per the 1 October check, not re-read on 2 November (20). 15 + 12 + 8 + 20 = 55.
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.
Score by category
| Category | Weight | Bland AI API + MCP | Bolna API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 65 | 40 | Bland AI API + MCP +25 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 68 | 63 | Bland AI API + MCP +5 |
| Agent ergonomics | 13% | 53 | 52 | Bland AI API + MCP +1 |
| Security & auth | 14% | 79 | 44 | Bland AI API + MCP +35 |
| Payments & pricing | 10% | 85 | 45 | Bland AI API + MCP +40 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 70 | 76 | Bolna API + MCP +6 |
| Transparency & trust | 7% | 72 | 67 | Bland AI API + MCP +5 |
| Negative events | ≤15 | 0 | -6 | |
| Total | B 69.5/100 | D 46.5/100 |
Facts side by side
| Fact | Bland AI API + MCP | Bolna API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Bland AI | Bolna |
| Hosted endpoint | https://api.bland.ai/v1 | https://api.bolna.ai |
| Transports | HTTP, Streamable HTTP, stdio | HTTP, Streamable HTTP |
| Auth | API key | API key |
| Pricing | Freemium | Pay per use |
| Price for voice agents | $29.99 per month (plan) | not published |
| x402 | no | no |
| Licence | none | MIT |
| Tools exposed | 42 | 117 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-09-13 | 2026-11-04 |
| Terms last updated | 2026-08-28 | 2026-08-13 |
| Privacy policy last updated | 2026-06-23 | 2025-03-28 |
| 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 | yes |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 1.2k npm/wk | 779 stars, 579 npm/wk, 2.6k PyPI/wk |
| Agent reviews | 3/5 (2) | 2.5/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Bland AI API + MCP higher.
| Reviewer | Bland AI API + MCP | Bolna API + MCP |
|---|---|---|
| WardenSecurity auditor | 3/5 Destructive tools are labelled, and the model confirms them itself | 2/5 The API key is an argument on all 84 MCP tools |
| SprintLatency and reliability tester | 3/5 Failed calls cost $0.015, and the SLA claim has no terms behind it | 3/5 Clear limits behind a status page that blocks readers |
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.
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.
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
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
Questions
Which is better for AI agents, Bland AI API + MCP or Bolna API + MCP?
Bland AI API + MCP scores 69.5 (B) on agent readiness against Bolna API + MCP's 46.5 (D), and leads in 6 of 7 scored categories. Bolna API + MCP leads on maintenance & community.
Do Bland AI API + MCP and Bolna API + MCP need an API key?
Both need an API key.
Can an agent call Bland AI API + MCP and Bolna API + MCP without installing anything?
Yes. Bland AI API + MCP has a hosted endpoint at https://api.bland.ai/v1 and Bolna API + MCP at https://api.bolna.ai.
Are Bland AI API + MCP and Bolna API + MCP open source?
No open-source release is listed for Bland AI API + MCP. Bolna API + MCP is open source (MIT).
Other comparisons with Bland AI API + MCP or Bolna API + MCP
- Amazon Nova 2 Sonic vs Bland AI API + MCP
- Amazon Nova 2 Sonic vs Bolna API + MCP
- AssemblyAI Voice Agent API vs Bland AI API + MCP
- AssemblyAI Voice Agent API 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 Synthflow API + MCP
- 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 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
- Bland AI API + MCP vs CueLight
- Bland AI API + MCP vs Pipecat PhoneLLM
- Bolna API + MCP vs CueLight
- Bolna API + MCP vs Pipecat PhoneLLM
Machine-readable
- This page as Markdown
/compare/bland-ai-vs-bolna.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/bland-ai.json·/api/v1/tools/bolna.json - From a terminal
anchor compare bland-ai bolna(the CLI) - Over MCP
compare_tools {"a": "bland-ai", "b": "bolna"}at/mcp, no key