The DropJune 29, 2026via Vercel Blog

Build realtime voice agents on AI Gateway

Why it matters

Vercel's AI Gateway now supports realtime voice agents alongside text/image/video, lowering the friction for developers to build multimodal AI applications with unified routing, observability, and cost controls across all modalities.

Key signals

  • Audio/voice support added to Vercel AI Gateway
  • Supports realtime voice, text-to-speech, and speech-to-text via single API calls
  • Models from OpenAI and xAI available
  • Features: server-side voice activity detection (VAD), barge-in interruption, mid-conversation tool calls
  • Available in AI SDK 7 (beta)
  • Browser integration via useRealtime hook with WebSocket authentication
  • Single API key for text, image, video, and audio routing with unified provider support, observability, and spend controls

The hook

Not a pilot. Vercel just unified voice, text, and video through a single API Gateway—same auth, same observability, same spend controls.

now supports audio/voice. You can add realtime voice, text to speech, and speech to text with the same calls you already use for text, image, and video, routed through AI Gateway alongside every other modality.AI Gateway Audio launches with models from and . Each call gets the same provider routing, observability, spend controls, and bring-your-own-key support you already use for your other models.OpenAIxAI These capabilities are in beta and available in 7.AI SDK Realtime, speech, and transcription model are supported on .AI SDK 7 Realtime turns your app into something a user can hold a conversation with. When they speak, the model responds right away. Because it replies in the moment instead of waiting for a full turn, users can interrupt and talk over it the way they would with a person. It fits voice assistants, customer support agents, hands-free tools, and anywhere a user would rather talk than type. What sets it apart from chaining models together is that a single realtime model hears audio and produces audio directly, instead of running a speech-to-text, then language model, then text-to-speech pipeline. In the browser, the hook manages the WebSocket connection, microphone capture, and audio playback.useRealtime The connection is authenticated with your AI Gateway credential, so you mint a short-lived token on the server and hand the browser only that token. Your API key never reaches the client. Add a route that mints the token: Then connect from a client component: The hook captures the microphone, streams the audio to the model through AI Gateway, and plays back the spoken reply. Outside the browser, you can drive the session over a WebSocket yourself with , , and . See the for that path.getWebSocketConfigserializeClientEventparseServerEventrealtime reference A realtime session works differently from a normal model call: Generate spoken audio from text with . Pass a voice and an output format, then write the result to a file:generateSpeech Transcribe r...

Get stories like this every Friday.

The 5 AI stories that matter — free, in your inbox.

Free forever. No spam.