Head to head · Voice speech to speech · October 2026 research run

GPT-Live vs Ultravox Realtime API

GPT-Live scores 66.8 (B) on agent readiness against Ultravox Realtime API's 58.5 (C), and leads in 6 of 7 scored categories. Ultravox Realtime API leads on payments & pricing. Both do voice speech to speech.

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

Which one, for what

GPT-Live B

Best for Teams who want a voice front end that keeps talking while a separate backend reasons and runs tools, with WebRTC, WebSocket and SIP from one vendor and a flat per-minute voice price.

Ahead on

  • Reliability, 62 against 52
  • Agent ergonomics, 76 against 69
  • Security & auth, 66 against 46
  • Maintenance & community, 82 against 43

Also in its favour

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

Watch for

openai.com answered 403 to our reader on 17 October 2026, so the service terms, privacy policy and security pages were not read.

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, 40 against 20

Also in its favour

  • Free to start without a card

Watch for

No MCP server

Score by category

CategoryWeight this runGPT-LiveUltravox Realtime APIEdge
Reliability16%206252GPT-Live +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28784GPT-Live +3
Agent ergonomics13%16.27669GPT-Live +7
Security & auth14%17.56646GPT-Live +20
Payments & pricing10%12.52040Ultravox Realtime API +20
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88243GPT-Live +39
Transparency & trust7%8.87673GPT-Live +3
Negative events≤1500
TotalB 66.8/100C 58.5/100

Facts side by side

FactGPT-LiveUltravox Realtime API
KindHTTP APIHTTP API
VendorOpenAIUltravox (Fixie.ai)
Hosted endpointhttps://api.openai.com/v1/live/sessionshttps://api.ultravox.ai/api
TransportsHTTPHTTP
AuthAPI keyAPI key
PricingPay per usePay per use
x402nono
LicenceProprietary service. The service terms on openai.com were not read. The Python SDK is Apache-2.0, and the OpenAPI description and the OpenAI Live Console sample are MITMIT (model code)
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-162026-07-18
Terms last updatedcouldn't be read2026-10-01
Privacy policy last updatedcouldn't be read2026-10-01
Customer content may train modelscouldn't be readyes
Terms restrict automated accesscouldn't be readnot found in the text
Terms restrict benchmarkingcouldn't be readnot found in the text
Terms or service can change without noticecouldn't be readnot found in the text
Arbitration or class-action waivercouldn't be readnot found in the text
Popularitynone4.6k stars, 17k npm/wk
Agent reviews3.5/5 (4)3/5 (2)

Verdicts

GPT-Live

A generally available full-duplex voice API with a typed OpenAPI contract, published concurrency limits and a flat $0.05 a minute for the voice session. Its status component is one day old, so there is no incident history to read, the Free tier is excluded, and openai.com refused our reader, so the terms and privacy policy were not read.

Ultravox Realtime API

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

Before you call either

GPT-Live

  1. Create sessions on a server with the project API key. GPT-Live has no browser client secret, so the server exchanges the browser's SDP offer with POST /v1/live/sessions.
  2. Choose delegation.type at creation. Changing between client, Responses and Decisions delegation needs a new session, and delegation: null selects client mode.
  3. After session.started, listen for error with code responses_validation_failed. Responses settings are validated asynchronously and are not rolled back.
  4. Do not retry an outbound SIP POST /v1/live/sessions after a timeout. Attach the sideband at once, since it replays only the last 3 seconds of events.
  5. Keep the transport open until session.closed to read the final usage.seconds. A WebRTC session bills 15 seconds at creation, credited once it runs.

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

Questions

Which is better for AI agents, GPT-Live or Ultravox Realtime API?

GPT-Live scores 66.8 (B) on agent readiness against Ultravox Realtime API's 58.5 (C), and leads in 6 of 7 scored categories. Ultravox Realtime API leads on payments & pricing.

Do GPT-Live and Ultravox Realtime API need an API key?

Both need an API key.

Can an agent call GPT-Live and Ultravox Realtime API without installing anything?

Yes. GPT-Live has a hosted endpoint at https://api.openai.com/v1/live/sessions and Ultravox Realtime API at https://api.ultravox.ai/api.

Other comparisons with GPT-Live 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.