OpenAI graduates the Realtime API and bolts on remote MCP servers and SIP telephony
OpenAI took the Realtime API out of beta on Thursday with a new gpt-realtime speech-to-speech model and three additions that matter for plumbing: remote MCP server support, meaning you pass an MCP server URL into the session config and the API handles tool calls itself; image input; and Session Initiation Protocol support for phones, PBXs and desk endpoints. Function calling on the ComplexFuncBench audio eval rose to 66.5% from 49.7% on the December 2024 model, instruction following on MultiChallenge audio to 30.5% from 20.6%, and two API-only voices, Cedar and Marin, shipped alongside.
Pricing fell 20% against gpt-4o-realtime-preview to $32 per million audio input tokens — $0.40 when cached — and $64 per million audio output tokens. Sessions also gained token limits and multi-turn truncation controls, and long-running function calls no longer disrupt a live conversation.

WHY IT MATTERS
MCP over a telephony transport is the milestone: a phone number can now be an agent endpoint that discovers tools from a remote MCP server without you hand-wiring integrations, which collapses telephony, tool routing and model into one session. At $64 per million audio output tokens, verbosity is a pricing decision as much as a UX one — cache-friendly input at $0.40 and hard token limits are now the levers that keep a talkative agent affordable.
