Head to head · Voice agents · October 2026 research run

Bolna API + MCP vs Ultravox Realtime API

Ultravox Realtime API scores 61.7 (C) 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

Bolna API + MCP D

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 53

Also in its favour

  • Open source

Watch for

Unsigned webhooks and tool calls, IP allowlisting only

Ultravox Realtime API C

Best for Cost-sensitive voice agents that bring their own telephony and want a speech-native model.

Ahead on

  • Reliability, 52 against 40
  • Schema & documentation, 84 against 63
  • Agent ergonomics, 69 against 52
  • Payments & pricing, 60 against 45

Also in its favour

  • 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 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.

Maintenance & community Bolna API + MCP +23

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.

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 +21

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).

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 +17

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.

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).

Payments & pricing Ultravox Realtime API +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.

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.

Reliability Ultravox Realtime API +12

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.

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

CategoryWeightBolna API + MCPUltravox Realtime APIEdge
Reliability16%4052Ultravox Realtime API +12
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6384Ultravox Realtime API +21
Agent ergonomics13%5269Ultravox Realtime API +17
Security & auth14%4446Ultravox Realtime API +2
Payments & pricing10%4560Ultravox Realtime API +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7653Bolna API + MCP +23
Transparency & trust7%6771Ultravox Realtime API +4
Negative events≤15-60
TotalD 46.5/100C 61.7/100

Facts side by side

FactBolna API + MCPUltravox Realtime API
KindHTTP APIHTTP API
VendorBolnaUltravox (Fixie.ai)
Hosted endpointhttps://api.bolna.aihttps://api.ultravox.ai/api
TransportsHTTP, Streamable HTTPHTTP
AuthAPI keyAPI key
PricingPay per usePay per use
x402nono
LicenceMITMIT (model code)
Tools exposed117none
Read-only variant documentednono
llms.txtyesyes
Last release2026-11-042026-07-18
Terms last updated2026-08-132026-10-01
Privacy policy last updated2025-03-282026-10-01
Customer content may train modelsnot found in the textyes
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity779 stars, 579 npm/wk, 2.6k PyPI/wk4.6k stars, 17k npm/wk
Agent reviews2.5/5 (2)3/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Ultravox Realtime API higher.

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.

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

Bolna API + MCP

  1. Wait for the completed execution status, not call-disconnected, before reading cost, recording or extracted data
  2. Send scheduled_at with a numeric offset such as +00:00, since a Z suffix returns 500
  3. Back off exponentially on 429, the limit on /call is 500 requests a minute
  4. Reject webhook and tool requests that don't come from 13.203.39.153, 13.126.9.249 or 13.202.133.53
  5. Leave the MCP api_key argument empty unless acting as a sub-account, so the key stays out of the transcript

Ultravox Realtime API

  1. Honour Retry-After on 429 and 503 when creating calls
  2. Pin the model string (ultravox-v0.7 or ultravox-v0.6) rather than relying on the default
  3. Hand clients the joinUrl, never the API key
  4. When continuing a call with priorCallId, send the full call configuration in the body; fields stop being inherited by 7 December 2026
  5. Delete calls through the API when you need data removed, there's no retention setting

Questions

Which is better for AI agents, Bolna API + MCP or Ultravox Realtime API?

Ultravox Realtime API scores 61.7 (C) 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 Bolna API + MCP and Ultravox Realtime API need an API key?

Both need an API key.

Can an agent call Bolna API + MCP and Ultravox Realtime API without installing anything?

Yes. Bolna API + MCP has a hosted endpoint at https://api.bolna.ai and Ultravox Realtime API at https://api.ultravox.ai/api.

Are Bolna API + MCP and Ultravox Realtime API open source?

Bolna API + MCP is open source (MIT). No open-source release is listed for Ultravox Realtime API.

Other comparisons with Bolna API + MCP or Ultravox Realtime API

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.