AI Models — March 2026
Gemini 3.1 Flash Ships
Native Audio via WebSocket.
Gemini 3.1 Flash Live adds native audio input/output over WebSocket with sub-300ms end-to-end latency.
Sources: Google DeepMind Gemini 3.1 Flash documentation; Google AI Studio WebSocket API reference; March 2026.
Google DeepMind released Gemini 3.1 Flash Live in March 2026, adding native audio input and output over a WebSocket API with a target end-to-end latency below 300 milliseconds. The model processes raw PCM audio directly rather than routing audio through a separate automatic speech recognition system. This matters because the separate ASR step adds latency, discards prosodic information (intonation, speaking rate, emotional tone), and introduces error accumulation across two model pipelines.
How the Architecture Eliminates the Pipeline
Traditional voice AI systems process audio through a sequential pipeline: Voice Activity Detection (VAD) identifies when the user is speaking, Speech-to-Text (STT) converts audio to text, the LLM processes the text and generates a response, and Text-to-Speech (TTS) converts the response back to audio. Each stage adds latency. VAD adds 50 to 200ms. STT adds 200 to 500ms. LLM processing adds 500ms to 2s. TTS adds 100 to 300ms. Total pipeline latency: 850ms to 3 seconds before the user hears the first word of a response.
Gemini 3.1 Flash Live processes audio natively. The model accepts raw audio input and generates raw audio output without intermediate text conversion. The bidirectional WebSocket stream means audio flows continuously in both directions: the model can begin responding while the user is still speaking. The latency reduction is structural, not incremental: eliminating four pipeline stages removes 500ms to 2 seconds of processing time.
Why Native Audio Processing Changes the Architecture
The 90.8% ComplexFuncBench Score
ComplexFuncBench Audio tests whether a voice AI can correctly execute complex function calls when instructions are delivered verbally. The benchmark is harder than text-based function calling because spoken instructions are ambiguous and contain filler words. Gemini 3.1 Flash Live’s 90.8% score means it correctly interprets and executes complex voice commands roughly 9 out of 10 times.
For developers building voice-activated applications, the 90.8% accuracy on complex function calls is the number that matters, not the latency reduction. The combination of low latency AND high accuracy on function calling is what makes Flash Live suitable for production voice applications: customer service agents, voice-activated search, voice-controlled enterprise workflows.
Search Live and the 200-Country Rollout
Google deployed Flash Live as the backend for Search Live, a voice-first search experience available in 200+ countries and 40+ languages. Users can have a spoken conversation with Google Search: ask questions, receive spoken answers, ask follow-ups, all through continuous voice interaction rather than typed queries.
The 200-country rollout is the distribution advantage that no competing voice AI product can match. OpenAI’s Advanced Voice Mode is limited to ChatGPT subscribers. Amazon’s Alexa+ is limited to the Alexa ecosystem. Google Search Live is available to anyone with a browser in 200 countries with no subscription required.
What the WebSocket API Enables for Developers
The WebSocket transport is a standard bidirectional streaming protocol. The API accepts raw PCM audio in 16-bit, 16kHz chunks. The model begins generating an audio response before the input audio stream ends. Search grounding is available during the audio session, meaning the model can retrieve live web search results and incorporate them into spoken responses in real time.
The competitive implication for developers: voice AI applications built on other platforms must compete against a voice experience that Google bundles for free into the world’s most-used search engine. The platform choice for voice AI development in 2026 is becoming a choice between Google’s ecosystem (native audio, high accuracy, massive distribution) and everyone else’s (text-bridged audio, lower accuracy, limited distribution).
The sub-300ms latency target puts Gemini 3.1 Flash Live in the same range as human conversational response times. Whether it consistently hits that target in production under load is the question that developer adoption will answer over the next 90 days. The architecture is right. The WebSocket API is the correct transport choice. The native audio processing eliminates the latency floor imposed by sequential pipelines.
Sources: Google DeepMind Gemini 3.1 Flash technical documentation; Google AI Studio WebSocket API reference; Gemini API changelog, March 2026.