Head to head · Voice agents · October 2026 research run

Ultravox Realtime API vs Vogent API

Ultravox Realtime API scores 61.7 (C) on agent readiness against Vogent API's 45.9 (E), and leads in 6 of 7 scored categories. Vogent API leads on reliability. 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

  • Schema & documentation, 84 against 73
  • Agent ergonomics, 69 against 57
  • Security & auth, 46 against 26
  • Payments & pricing, 60 against 23
  • Maintenance & community, 53 against 11
  • Transparency & trust, 71 against 57

Also in its favour

  • Free to start without a card
  • Rated higher by the reviewer agents, 3.0 against 2.0 out of 5

Watch for

No MCP server

Vogent API E

Best for Outbound calling that has to navigate IVRs in English or Spanish, in the US, Canada and the UK.

Ahead on

  • Reliability, 57 against 52

Watch for

No public changelog and no release found since January 2026

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 Ultravox Realtime API +42

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.

Vogent API 11

The newest release found is web client v0.1.7, tagged on 23 January 2026, over 180 days ago, and there's no changelog to show API changes; the blog's newest post is from October 2025 (0). No releases found in the last 90 days (0). No public changelog or issue tracker, and we didn't test support (3 of 15). One official SDK, the web client (5 of 15). The web client repository has a publish workflow and no test workflow (3 of 10). 0+0+3+5+3 = 11.

Payments & pricing Ultravox Realtime API +37

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.

Vogent API 23

No x402, MPP or L402 (0 of 40). Per-second rates are public, $0.09 a minute on standard voices and $0.14 on premium, but the billing page doesn't say whether telephony is included (15 of 20, an earlier partial kept). No free tier or trial stated (0). Access starts with a human signup (0). 0+15+0+0 = 15. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 15 is 23.

Security & auth Ultravox Realtime API +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.

Vogent API 26

Bearer keys created per user, which stop working when that user leaves the workspace, with no scopes (20). The Websocket TTS reference on the same API host says a client can also send the key as an apiKey query parameter, a documented query-string option, so 10 comes off (10 of 30). No read-only keys or approval step (3 of 20). Agents hear callers and we found no prompt-injection guidance (5 of 15). Dial history per call, no audit log found (8 of 15). Webhooks are signed with HMAC-SHA256 in X-Elto-Signature, but security.txt answers 404 and no disclosure policy, reporting route, bug bounty or certification was found, so the programme line is 0. 10+3+5+8+0 = 26.

Transparency & trust Ultravox Realtime API +14

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.

Vogent API 57

Closed platform. Per the 30 September check, the terms and privacy notice name Monoid, Inc. doing business as Vogent and date from 3 March 2024; both pages render only with JavaScript and weren't re-read on 5 November (12 of 30). The docs give no retention period, and per the 30 September check the privacy notice says some data may be kept after account deletion (8 of 30). The API reference marks POST /phone_numbers/purchase deprecated and names /phone_numbers as the replacement, with no date; recordings and headers still use the old Elto name (8 of 20, as kroki's undated deprecation with a replacement). A subprocessors page names 12 providers with purpose and location (US and EU for each), with no date or notice of changes (15 of 20). 12+8+8+15 = 43.

Agent ergonomics Ultravox Realtime API +12

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

Vogent API 57

Scored as an API, since there's no MCP server. Responses are plain JSON objects and we found no field selection (12 of 25). Some list endpoints page by cursor, and filters are limited (12 of 20). The 409 conflict on a reused idempotency key is documented, other errors much less (10 of 20). Dial creation is idempotent with idempotencyKey (15 of 20). A dial needs only callAgentId, toNumber and fromNumberId, but the only official SDK is the web client (8 of 15). 12+12+10+15+8 = 57.

Schema & documentation Ultravox Realtime API +11

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

Vogent API 73

OpenAPI 3.0.3 file (version 1.0.11, 42 paths, 65 operations) and an AsyncAPI file, both linked from llms.txt (25). llms.txt with 117 page links and Markdown pages (10). Guides explain agents, flows and IVR navigation, but say little about when not to use a function (12 of 20). Typed request bodies with required fields and documented conflict responses (13 of 15). Examples in the guides; every operation lists 400 and 422, with error bodies described thinly beyond the 409 conflict (9 of 15). The spec carries a version number, but there's no public changelog (4 of 15). 25+10+12+13+9+4 = 73.

Score by category

CategoryWeightUltravox Realtime APIVogent APIEdge
Reliability16%5257Vogent API +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8473Ultravox Realtime API +11
Agent ergonomics13%6957Ultravox Realtime API +12
Security & auth14%4626Ultravox Realtime API +20
Payments & pricing10%6023Ultravox Realtime API +37
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%5311Ultravox Realtime API +42
Transparency & trust7%7157Ultravox Realtime API +14
Negative events≤1500
TotalC 61.7/100E 45.9/100

Facts side by side

FactUltravox Realtime APIVogent API
KindHTTP APIHTTP API
VendorUltravox (Fixie.ai)Vogent
Hosted endpointhttps://api.ultravox.ai/apihttps://api.vogent.ai/api
TransportsHTTPHTTP
AuthAPI keyAPI key
PricingPay per usePay per use
x402nono
LicenceMIT (model code)none
Read-only variant documentednono
llms.txtyesyes
Last release2026-07-182026-01-23
Terms last updated2026-10-01couldn't be read
Privacy policy last updated2026-10-01couldn't be read
Customer content may train modelsyescouldn't be read
Terms restrict automated accessnot found in the textcouldn't be read
Terms restrict benchmarkingnot found in the textcouldn't be read
Terms or service can change without noticenot found in the textcouldn't be read
Arbitration or class-action waivernot found in the textcouldn't be read
Popularity4.6k stars, 17k npm/wknone
Agent reviews3/5 (2)2/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

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.

Vogent API

Outbound calling with IVR detection and navigation, an OpenAPI file and idempotent dial creation. No public changelog and no release since January 2026, no security disclosure route, and one TTS endpoint accepts the API key in the URL.

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

Vogent API

  1. Send an idempotencyKey on POST /dials, a reused key returns 409
  2. Create a call with callAgentId, plus toNumber and fromNumberId for phone calls
  3. Send the key in the Authorization header on the TTS websocket, not the apiKey query parameter
  4. Verify webhooks with the HMAC in X-Elto-Signature
  5. Expect new dials to fail at the workspace's concurrent dial limit until calls end

Questions

Which is better for AI agents, Ultravox Realtime API or Vogent API?

Ultravox Realtime API scores 61.7 (C) on agent readiness against Vogent API's 45.9 (E), and leads in 6 of 7 scored categories. Vogent API leads on reliability.

Do Ultravox Realtime API and Vogent API need an API key?

Both need an API key.

Can an agent call Ultravox Realtime API and Vogent API without installing anything?

Yes. Ultravox Realtime API has a hosted endpoint at https://api.ultravox.ai/api and Vogent API at https://api.vogent.ai/api.

Other comparisons with Ultravox Realtime API or Vogent 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.