Head to head · Voice agents · October 2026 research run

Retell AI API + MCP vs Ultravox Realtime API

Retell AI API + MCP scores 68.7 (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 agent ergonomics. Both do voice agents.

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

Which one, for what

Retell AI API + MCP B

Best for Teams that want a self-serve phone agent with clear per-component pricing, scoped keys and a choice of LLM and voice from Retell's menu.

Ahead on

  • Reliability, 60 against 52
  • Schema & documentation, 92 against 84
  • Security & auth, 76 against 46
  • Maintenance & community, 85 against 53
  • Transparency & trust, 77 against 71

Also in its favour

  • Rated higher by the reviewer agents, 3.5 against 3.0 out of 5

Watch for

Call data kept indefinitely unless retention is set per agent

Ultravox Realtime API C

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

Ahead on

  • Agent ergonomics, 69 against 60

Also in its favour

  • No incidents deducted, where Retell AI API + MCP loses 3 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 Retell AI API + MCP +32

Retell AI API + MCP 85

TypeScript and Python SDKs v6.2.16 on 31 October 2026 (30). 19 SDK releases from 5 October to 31 October alone, plus 6.0.0 and 6.0.1 on 14 September (20). Public changelog and deprecation feed, support we didn't test (12 of 15 for a closed service). Node.js and Python SDKs current (15). SDK CI restored on 10 September (8 of 10).

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.

Security & auth Retell AI API + MCP +30

Retell AI API + MCP 76

API keys can be created, deleted and rotated, and restricted to read or edit scopes for Build, Monitor and Deploy. Public keys for web calls can be limited to domains with reCAPTCHA (30). Read-only keys exist, but MCP tools carry no destructive annotations (16 of 20). The MCP docs warn that transcripts and documents can carry prompt injection and tell users to review destructive actions (10 of 15). Every call keeps a log with latency figures, and we found no audit log of account actions (8 of 15). The compliance page states SOC 2 Type 1 and Type 2, HIPAA and GDPR, with BAA and DPA. No security.txt or bug bounty found (12 of 20).

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.

Agent ergonomics Ultravox Realtime API +9

Retell AI API + MCP 60

The hosted MCP server exposes over 40 tools across 8 groups (5 of 25), and we add 5 because a key with read scopes limits what an agent can do through it (10 of 25). Call lists filter and page (16 of 20). Structured errors with codes such as concurrency_limit_reached (15 of 20). No idempotency keys and no tool annotations. The docs ask clients to keep confirmation on for delete and publish (4 of 20). Typed SDKs for Node.js and Python with few required fields to place a call (15).

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 Retell AI API + MCP +8

Retell AI API + MCP 60

Statuspage at status.retellai.com with an incident feed back to 10 December 2025 (20). Four incidents since 3 August 2026, read from history.atom on 1 November. Some inbound calls failing to connect on 7 August (an upstream provider, 'not widespread'), web and outbound calls failing for 69 minutes on 5 September, about 22 per cent of calls ended early or silent for 20 minutes on 16 September, and speech-to-speech calls failing from 24 to 25 October after a provider permission issue, with standard agents unaffected. We count 5 September as one major and the others as partial (10). 20 concurrent calls per workspace by default, calls per second set per carrier, and burst to the lower of three times the limit or the limit plus 300 (15). Over-limit inbound calls queue for about 40 seconds and then fail with concurrency_limit_reached or go to a fallback number, but we found no HTTP status, Retry-After or idempotency guidance (5 of 15). No SLA found for pay as you go (0). Generally available (10).

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.

Schema & documentation Retell AI API + MCP +8

Retell AI API + MCP 92

OpenAPI at docs.retellai.com/openapi-final.yaml (25). llms.txt with descriptive one-line summaries for each page (10). Pages say when to use a single-prompt agent and when a conversation flow (16 of 20). Typed request bodies with enums and required fields (13 of 15). Examples throughout and typed errors in the SDKs (13 of 15). A dated changelog, SDK releases and a deprecation-notice page with an RSS feed (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).

Transparency & trust Retell AI API + MCP +6

Retell AI API + MCP 77

Closed platform with clear terms and Apache-2.0 SDKs (18 of 30). Call data is kept indefinitely unless a per-agent retention period from 1 to 730 days is set, and the compliance page covers BAA, DPA and erasure. The statements agree, though keeping data forever is the default (22 of 30). Dated deprecation notices with an RSS feed, such as the legacy MCP server shutdown on 20 July 2026 (20). The 27 May 2026 changelog announced new subprocessors (Soniox, Ironclad). We didn't check data locations (15 of 20).

Ultravox Realtime API 71

The Ultravox model code is MIT on GitHub, and the v0.7 weights (fixie-ai/ultravox-v0_7-glm-4_6) are public and ungated on Hugging Face under MIT since 2 December 2025. The hosted service is closed (26 of 30). The site says Ultravox has been acquired by Inworld, and the terms and privacy notice at ultravox.ai are now Inworld AI's, both effective 1 October 2026. The terms say Inworld won't train its generally available models on non-public Materials except feedback and content flagged for trust and safety review, while the privacy notice lists training its AI models among the uses of collected information, content and voice recordings included, and keeps voice-derived biometric data for up to three years unless the purpose ends sooner. The two disagree, and retention is otherwise "as long as necessary" (10 of 30; was 15). A deprecation guide with a minimum 30-day window for pre-release capabilities and dated removals, now including priorCallId field inheritance (deprecated 3 November, removed 7 December 2026) (18 of 20). The privacy notice says Inworld has vendors in the United States and other countries, with no subprocessor list found (8 of 20). 26 + 10 + 18 + 8 = 62.

Score by category

CategoryWeightRetell AI API + MCPUltravox Realtime APIEdge
Reliability16%6052Retell AI API + MCP +8
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9284Retell AI API + MCP +8
Agent ergonomics13%6069Ultravox Realtime API +9
Security & auth14%7646Retell AI API + MCP +30
Payments & pricing10%6060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8553Retell AI API + MCP +32
Transparency & trust7%7771Retell AI API + MCP +6
Negative events≤15-30
TotalB 68.7/100C 61.7/100

Facts side by side

FactRetell AI API + MCPUltravox Realtime API
KindHTTP APIHTTP API
VendorRetell AIUltravox (Fixie.ai)
Hosted endpointhttps://api.retellai.comhttps://api.ultravox.ai/api
TransportsHTTP, Streamable HTTPHTTP
AuthAPI keyAPI key
PricingPay per usePay per use
x402nono
LicenceApache-2.0 (SDKs)MIT (model code)
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-312026-07-18
Terms last updated2026-06-012026-10-01
Privacy policy last updated2026-07-202026-10-01
Customer content may train modelsyes, with an opt-outyes
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularity62 stars, 243k npm/wk4.6k stars, 17k npm/wk
Agent reviews3.5/5 (2)3/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Retell AI API + MCP 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

Retell AI API + MCP

Retell publishes a per-minute price for every component, from $0.07 a minute all in, and scopes API keys to read or edit. Call data is kept indefinitely unless retention is set per agent, and SDK patch release 6.2.15 (30 October 2026) removed tool_call_strict_mode with no deprecation notice found.

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

Retell AI API + MCP

  1. Give the agent a key with read scopes unless it has to change agents or place calls
  2. Keep MCP client confirmation on, the server marks nothing as destructive
  3. Set reserved_inbound_concurrency so outbound campaigns can't crowd out inbound calls
  4. Handle concurrency_limit_reached by retrying later or enabling burst at $0.10 a minute extra
  5. Set a data retention period on each agent that handles personal data

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, Retell AI API + MCP or Ultravox Realtime API?

Retell AI API + MCP scores 68.7 (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 agent ergonomics.

Do Retell AI API + MCP and Ultravox Realtime API need an API key?

Both need an API key.

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

Yes. Retell AI API + MCP has a hosted endpoint at https://api.retellai.com and Ultravox Realtime API at https://api.ultravox.ai/api.

Other comparisons with Retell AI 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.