Head to head · Voice agent · October 2026 research run

Ultravox Realtime API vs Vogent API

Ultravox Realtime API has a score of 58.6 (C) against Vogent API's 47.4 (D). Both do voice agent. The largest gap is maintenance & community, 32 points.

Which one, for what

Pick Ultravox Realtime API for

  • schema & documentation (+11)
  • agent ergonomics (+12)
  • security & auth (+6)
  • payments & pricing (+25)
  • maintenance & community (+32)
  • transparency & trust (+29)

Pick Vogent API for

  • reliability (+10)

Score by category

CategoryWeight this runUltravox Realtime APIVogent APIEdge
Reliability16%205262Vogent API +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28473Ultravox Realtime API +11
Agent ergonomics13%16.26957Ultravox Realtime API +12
Security & auth14%17.54640Ultravox Realtime API +6
Payments & pricing10%12.54015Ultravox Realtime API +25
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.84311Ultravox Realtime API +32
Transparency & trust7%8.87546Ultravox Realtime API +29
Negative events≤1500
Total58.6 · C47.4 · D

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
Tools exposednonenone
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listednot listed
Last release2026-07-182026-01-23
Popularity4.6k stars, 17k npm/wk899 npm/wk
Agent reviews3/5 (2)2/5 (2)

Verdicts

Ultravox Realtime API

Flat $0.05 a minute including model and built-in voices. No MCP server.

Vogent API

IVR detection and navigation models for outbound calls. No public changelog and no release found since January 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. Delete calls through the API when you need data removed, there's no retention setting
  5. Use call stages for multi-step flows instead of one long prompt

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. Tell the model when to emit <|transfer|>, since transfers fire on that tag
  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

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.