Head to head · Voice agents · October 2026 research run

Ultravox Realtime API vs Vapi API + MCP

Vapi API + MCP scores 66.9 (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 payments & pricing. Both do voice agents.

Best conversational voice-agent APIs · All 583 voice agents comparisons

Which one, for what

Ultravox Realtime API C

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

Ahead on

  • Payments & pricing, 60 against 53

Also in its favour

  • Rated higher by the reviewer agents, 3.0 against 2.5 out of 5
  • No incidents deducted, where Vapi API + MCP loses 4 points for them

Watch for

No MCP server

Vapi API + MCP B

Best for Developers who want to choose every provider, bring their own keys and tune cost against latency.

Ahead on

  • Reliability, 70 against 52
  • Schema & documentation, 89 against 84
  • Security & auth, 61 against 46
  • Maintenance & community, 88 against 53

Also in its favour

  • Runs on your own machine

Watch for

Real per-minute cost depends on provider choices

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 Vapi API + MCP +35

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.

Vapi API + MCP 88

The changelog's newest entry is the week of 26 October 2026, and @vapi-ai/web 3.1.0 was tagged on 30 October (30). Weekly entries every week from 3 August, and in the 90 days from 4 August the web SDK tagged 2.6.2, 2.6.3, 2.7.0, 2.7.1, 3.0.0, 3.0.1 and 3.1.0, the Python SDK 3.0.0 (12 October), the TypeScript SDK 2.0.1 and the MCP server 0.0.10 and 0.0.11 (20). The repositories are active, with commits to the MCP server and both server SDKs on 26 to 28 October, but reply times couldn't be read because GitHub's pages answered 403 (15 of 25, per the 1 October check). Server SDKs, web SDK and MCP server on npm and PyPI (15). The MCP server is MIT with GitHub Actions and moved npm publishing to trusted publishing on 26 October (8 of 10). 30 + 20 + 15 + 15 + 8 = 88.

Reliability Vapi API + MCP +18

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.

Vapi API + MCP 70

status.vapi.ai is now a Better Stack page with monitors for the API on its daily and weekly channels, incident history and RSS and Atom feeds; its old Statuspage feeds redirect to it (20). In the 90 days from 4 August the feed lists twelve incidents. Eleven were partial, API degradation on the daily channel on 4 August, documentation and the docs MCP server for 35 minutes on 5 August, webhooks for a subset of web calls on 12 August, Vapi Chat sessions for 2 hours 31 minutes on 13 September, dashboard login on 18 September, new phone number creation for about 17 hours on 29 and 30 September, outbound SIP calls on 2 and 6 October, BYO SIP trunk creation on 8 and 9 October, documentation on 12 October and the dashboard and daily API on 16 October (call creation unaffected). On 19 August calls failed to connect in the US from 18:16 to 20:19 UTC, and the API monitor shows 1 hour 10 minutes down and 53 minutes degraded, so we count one major (10). The 1 October check dated that incident to 12 August. Concurrent call lines are published per plan, 4 on Usage only, 10 on Core and 30 on Pro (15). A full account queues the call and subscriptionLimits.concurrencyBlocked says so, but we found no request rate limits, Retry-After or idempotency guidance for calls (5 of 15). The Pro package carries a 99 per cent uptime SLA and Premier 99.9 per cent, re-read on 2 November (10). The API is generally available (10). 20 + 10 + 15 + 5 + 10 + 10 = 70.

Security & auth Vapi API + MCP +15

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.

Vapi API + MCP 61

Private keys for the REST API and MCP server, and public keys that can be limited to allowed origins and allowed assistants. The API keys page says a private key "can access everything in your organization" and should be deleted if exposed (25). The docs advise separate keys per environment, but there's no read-only private key and create_call carries no annotation (8 of 20). Assistants listen to callers. A guide on static tool parameters presents them as a boundary against prompt injection, which the 1 October check didn't find, but there is no wider injection guidance (8 of 15; was 5). Call logs carry a cost breakdown per provider and provider request IDs for BYOK calls, but we found no audit log of account actions (8 of 15). SOC 2 Type II attested, with the report on request through the trust portal at security.vapi.ai, and HIPAA, GDPR and PCI pages. vapi.ai/.well-known/security.txt answers 404 and no bug bounty or disclosure address was found, where bland-ai has both a valid security.txt and a disclosure address (17). The June 2026 npm incident was written up in public (12 of 20). 25 + 8 + 8 + 8 + 12 = 61.

Payments & pricing Ultravox Realtime API +7

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.

Vapi API + MCP 53

No x402, MPP or L402 (0 of 40). The $0.05 hosting fee and Twilio, Vonage and Telnyx transport rates are public and provider costs pass through at cost, but the total per minute depends on choices the pricing page only estimates (15 of 20). $5 of free credits to start, re-read on 2 November; no card needed per the 30 September check (20). Access starts with a human signup (0). 0 + 15 + 20 + 0 = 35. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.

Schema & documentation Vapi API + MCP +5

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

Vapi API + MCP 89

OpenAPI 3.1.0 at docs.vapi.ai/openapi/api-reference.json with 145 operations on 76 paths, linked from llms.txt. api.vapi.ai's robots.txt now disallows /api*, so the api.vapi.ai/api-json path the 1 October check read wasn't requested (25). llms.txt with Markdown copies of every page and a docs MCP server (10). Guides explain when to use squads, tools and fallback plans (15 of 20). The OpenAPI types every field, though assistant configuration is a large nested object (12 of 15). Examples throughout and a call-errors guide that explains ended reasons, with less on REST error bodies (12 of 15). A weekly changelog, now at docs.vapi.ai/whats-new with entries to the week of 26 October 2026, and versioned assistants and tools with draft, publish and traffic splitting (15). 25 + 10 + 15 + 12 + 12 + 15 = 89.

Score by category

CategoryWeightUltravox Realtime APIVapi API + MCPEdge
Reliability16%5270Vapi API + MCP +18
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8489Vapi API + MCP +5
Agent ergonomics13%6967Ultravox Realtime API +2
Security & auth14%4661Vapi API + MCP +15
Payments & pricing10%6053Ultravox Realtime API +7
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%5388Vapi API + MCP +35
Transparency & trust7%7175Vapi API + MCP +4
Negative events≤150-4
TotalC 61.7/100B 66.9/100

Facts side by side

FactUltravox Realtime APIVapi API + MCP
KindHTTP APIHTTP API
VendorUltravox (Fixie.ai)Vapi
Hosted endpointhttps://api.ultravox.ai/apihttps://api.vapi.ai
TransportsHTTPHTTP, Streamable HTTP, stdio
AuthAPI keyAPI key
PricingPay per usePay per use
x402nono
LicenceMIT (model code)MIT (MCP server)
Tools exposednone13
Read-only variant documentednono
llms.txtyesyes
Last release2026-07-182026-10-30
Terms last updated2026-10-012026-09-14
Privacy policy last updated2026-10-012023-09-09
Customer content may train modelsyesyes
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textyes
Popularity4.6k stars, 17k npm/wk57 stars, 177k npm/wk, 42k PyPI/wk
Agent reviews3/5 (2)2.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Ultravox Realtime API higher, the other way from the total score.

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

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.

Vapi API + MCP

Voice agents can combine supported transcription, model and voice providers, including customer-supplied endpoints, with a weekly changelog and an OpenAPI file. Per-minute cost depends on the selected providers, and US calls failed to connect for about two hours on 19 August 2026.

Before you call either

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

Vapi API + MCP

  1. Read subscriptionLimits.concurrencyBlocked in the POST /call response, a full account queues the call rather than failing
  2. Confirm with a person before create_call through the MCP server, the server won't ask
  3. Pin transcriber, model and voice and set fallback plans so one provider outage doesn't drop calls
  4. Read the call log's cost breakdown to see what each provider charged
  5. Check @vapi-ai/server-sdk isn't pinned to 0.11.1, 0.11.2, 1.2.1 or 1.2.2

Questions

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

Vapi API + MCP scores 66.9 (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 payments & pricing.

Do Ultravox Realtime API and Vapi API + MCP need an API key?

Both need an API key.

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

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

Other comparisons with Ultravox Realtime API or Vapi API + MCP

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.