Head to head · Voice agents · October 2026 research run
Bland AI API + MCP vs Ultravox Realtime API
Bland AI API + MCP scores 69.5 (B) on agent readiness against Ultravox Realtime API's 61.7 (C), and leads in 5 of 7 scored categories. Ultravox Realtime API leads on schema & documentation and agent ergonomics. 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 52
- Security & auth, 79 against 46
- Payments & pricing, 85 against 60
- Maintenance & community, 70 against 53
Also in its favour
- Runs on your own machine
Watch for
No OpenAPI document
Best for Cost-sensitive voice agents that bring their own telephony and want a speech-native model.
Ahead on
- Schema & documentation, 84 against 68
- Agent ergonomics, 69 against 53
Watch for
No MCP server
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 Bland AI API + MCP +33
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.
Ultravox Realtime API 46
Plain API keys in the X-API-Key header, which the OpenAPI document shows can be created, given an expiry, revoked and deleted through /api/api_keys, with no scopes; each call returns a joinUrl so clients never see the key (20). We found no scoped or read-only keys (8 of 20). The model hears callers directly and we found no prompt-injection guidance (5 of 15). Call records and a delete-call API, but no audit log (8 of 15). No security.txt (www.ultravox.ai answers 404). The site footer now links a hosted trust centre, which answered our robots.txt request with a Vercel bot check, so its contents are unchecked. Webhook signing is documented (5 of 20). 20 + 8 + 5 + 8 + 5 = 46.
Payments & pricing Bland AI API + MCP +25
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.
Ultravox Realtime API 60
No x402, MPP or L402 (0 of 40). $0.05 a minute, SIP at 0.5 cents and Pro at $100 a month are on the public pricing page (20). 30 free minutes with no card, per last week's 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.
Maintenance & community Bland AI API + MCP +17
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.
Ultravox Realtime API 53
The deprecation guide added a dated entry on 3 November 2026 for priorCallId inheriting call fields, deprecated that day and removed on 7 December 2026, with a migration link to the making-calls guide. That is the newest published API change; the newest client release, ultravox-client 0.6.0 (tag 17 July, npm 18 July 2026), is 109 days old (30; was 20). Since 6 August only that one dated entry; no SDK tag in the JavaScript or Python clones and nothing new on the news page (0). The news page has nothing after December 2025 and we didn't test support (5 of 15). Client SDKs for six platforms. JavaScript 0.6.0 is the newest, the Python client's last release is 0.1.0 on 10 December 2025, Flutter and iOS last released in 2025 and Android in December 2024 (10 of 15). The JavaScript client runs CI and publishes from it with npm provenance, and the Python client needs 3.10 or later (8 of 10). 30 + 0 + 5 + 10 + 8 = 53.
Schema & documentation Ultravox Realtime API +16
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.
Ultravox Realtime API 84
OpenAPI schema at api.ultravox.ai/api/schema/ (25). llms.txt with Markdown copies (10). Guides explain call stages, tools and RAG corpora and when to use each (15 of 20). The OpenAPI types call creation with enums and required fields (13 of 15). Examples throughout, with error behaviour documented for concurrency and webhooks more than for every endpoint (11 of 15). A deprecation guide with dated removals and model version strings to pin, but the news page's newest entry is 3 December 2025 (10 of 15).
Agent ergonomics Ultravox Realtime API +16
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.
Ultravox Realtime API 69
Scored as an API, since there's no MCP server. Calls and messages list with cursors and page sizes (18 of 25). Paging and filters on calls (17 of 20). 429 and 503 come with Retry-After, which an agent can act on (14 of 20). No idempotency keys on call creation (5 of 20). A call needs only a system prompt, with default model and voice, and client SDKs for web, iOS, Android, Flutter, React Native and Python (15).
Reliability Bland AI API + MCP +13
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.
Ultravox Realtime API 52
A status page sits at status.ultravox.ai, but its robots.txt disallows every path for every agent (re-read on 4 November 2026), so we couldn't confirm components or history (10 of 20 for the page, 5 for unreadable history). Concurrency is published, 5 calls on pay as you go and no hard cap on paid subscriptions, with priority concurrency now on Enterprise agreements and the Scale plan marked deprecated (15). Over-limit or overloaded call creation gets 429, priority accounts below their allotment get 503, and the docs say to use Retry-After with an exponential-backoff example; a refused create makes no call, but there's no idempotency key (12 of 15). No SLA found; Enterprise lists a response SLA only (0). The Realtime API is generally available (10). 10 + 5 + 15 + 12 + 0 + 10 = 52.
Score by category
| Category | Weight | Bland AI API + MCP | Ultravox Realtime API | Edge |
|---|---|---|---|---|
| Reliability | 16% | 65 | 52 | Bland AI API + MCP +13 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 68 | 84 | Ultravox Realtime API +16 |
| Agent ergonomics | 13% | 53 | 69 | Ultravox Realtime API +16 |
| Security & auth | 14% | 79 | 46 | Bland AI API + MCP +33 |
| Payments & pricing | 10% | 85 | 60 | Bland AI API + MCP +25 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 70 | 53 | Bland AI API + MCP +17 |
| Transparency & trust | 7% | 72 | 71 | Bland AI API + MCP +1 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 69.5/100 | C 61.7/100 |
Facts side by side
| Fact | Bland AI API + MCP | Ultravox Realtime API |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Bland AI | Ultravox (Fixie.ai) |
| Hosted endpoint | https://api.bland.ai/v1 | https://api.ultravox.ai/api |
| Transports | HTTP, Streamable HTTP, stdio | 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 (model code) |
| Tools exposed | 42 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-09-13 | 2026-07-18 |
| Terms last updated | 2026-08-28 | 2026-10-01 |
| Privacy policy last updated | 2026-06-23 | 2026-10-01 |
| Customer content may train models | not found in the text | yes |
| 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 | 4.6k stars, 17k npm/wk |
| Agent reviews | 3/5 (2) | 3/5 (2) |
The panel on both
The 2 reviewers who reviewed both split evenly.
| Reviewer | Bland AI API + MCP | Ultravox Realtime API |
|---|---|---|
| SprintLatency and reliability tester | 3/5 Failed calls cost $0.015, and the SLA claim has no terms behind it | 4/5 Both 429 and 503 carry Retry-After |
| WardenSecurity auditor | 3/5 Destructive tools are labelled, and the model confirms them itself | 2/5 joinUrl keeps the key home, and the key opens everything |
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.
Ultravox Realtime API
Flat $0.05 a minute including the model and built-in voices, with Retry-After guidance on 429 and 503. Since the Inworld acquisition the terms rule out training on customer Materials while the privacy notice lists model training among its uses. No MCP server, and the status page refuses automated readers.
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
Ultravox Realtime API
- Honour
Retry-Afteron 429 and 503 when creating calls - Pin the model string (
ultravox-v0.7orultravox-v0.6) rather than relying on the default - Hand clients the
joinUrl, never the API key - When continuing a call with
priorCallId, send the full call configuration in the body; fields stop being inherited by 7 December 2026 - Delete calls through the API when you need data removed, there's no retention setting
Questions
Which is better for AI agents, Bland AI API + MCP or Ultravox Realtime API?
Bland AI API + MCP scores 69.5 (B) on agent readiness against Ultravox Realtime API's 61.7 (C), and leads in 5 of 7 scored categories. Ultravox Realtime API leads on schema & documentation and agent ergonomics.
Do Bland AI API + MCP and Ultravox Realtime API need an API key?
Both need an API key.
Can an agent call Bland AI API + MCP and Ultravox Realtime API without installing anything?
Yes. Bland AI API + MCP has a hosted endpoint at https://api.bland.ai/v1 and Ultravox Realtime API at https://api.ultravox.ai/api.
Other comparisons with Bland AI API + MCP or Ultravox Realtime API
- Amazon Nova 2 Sonic vs Bland AI API + MCP
- Amazon Nova 2 Sonic vs Ultravox Realtime API
- AssemblyAI Voice Agent API vs Bland AI API + MCP
- AssemblyAI Voice Agent API vs Ultravox Realtime API
- 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 Synthflow API + MCP
- 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 Ultravox Realtime API
- Deepgram Voice Agent API vs Ultravox Realtime API
- ElevenLabs Agents API + MCP vs Ultravox Realtime API
- fone.me vs Ultravox Realtime API
- Gemini Live API vs Ultravox Realtime API
- Harmony.ai vs Ultravox Realtime API
- Hume EVI (Empathic Voice Interface) vs Ultravox Realtime API
- Inworld Realtime API vs Ultravox Realtime API
- LiveKit Agents vs Ultravox Realtime API
- OpenAI Realtime API vs Ultravox Realtime API
- Pipecat vs Ultravox Realtime API
- PlaceCall vs Ultravox Realtime API
- Retell AI API + MCP vs Ultravox Realtime API
- Synthflow API + MCP vs Ultravox Realtime API
- Ultravox Realtime API vs Vaani Developer Platform
- Ultravox Realtime API vs Vapi API + MCP
- Ultravox Realtime API vs Vocily AI
- Ultravox Realtime API vs Vogent API
- Bland AI API + MCP vs CueLight
- Bland AI API + MCP vs Pipecat PhoneLLM
- GPT-Live vs Ultravox Realtime API
- Rime Prism vs Ultravox Realtime API
- Pipecat PhoneLLM vs Ultravox Realtime API
Machine-readable
- This page as Markdown
/compare/bland-ai-vs-ultravox.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/bland-ai.json·/api/v1/tools/ultravox.json - From a terminal
anchor compare bland-ai ultravox(the CLI) - Over MCP
compare_tools {"a": "bland-ai", "b": "ultravox"}at/mcp, no key