
Gemini 3.8 Live with Live Avatar: Google Gives Its Voice Model a Face
- typesafeNEWTypeSafe: Jev 1.132026-09-24$0.04 / $0.00 per 1M tokens · 36 tok/s
- openaiNEWOpenAI: GPT-6 Luna2026-09-2237Intelligence
- openaiNEWOpenAI: GPT-6 Sol2026-09-2248Intelligence
- anthropicNEWAnthropic: Claude Opus 5.52026-09-2258Intelligence
- grokNEWGrok 4.72026-09-2146Intelligence
- OrcaNEWOrca: OrcaCyber Zero 1.02026-09-17$3.00 / $5.00 per 1M tokens · 181 tok/s
- orcaNEWOrca: OrcaVerify Text 1.02026-09-16$2.00 / $0.00 per 1M tokens · 1277 tok/s
- deepseekDeepSeek: DeepSeek V4.1 Flash2026-09-1040Intelligence
- openaiOpenAI: GPT-6 Astra2026-09-0453Intelligence77Coding
- googleGoogle: Gemini 3.8 Flash2026-09-0241Intelligence76Coding
- qwenQwen: Qwen3.8 Max (0902)2026-09-0245Intelligence76Coding
- anthropicAnthropic: Claude Fable 5.12026-09-0153Intelligence82Coding
- AlibabaQwen: Qwen3.8 Flash2026-08-26$0.15 / $0.47 per 1M tokens · 110 tok/s
- z-aiZ.ai: GLM 5.3 Flash2026-08-2642Intelligence72Coding
- DeepSeekDeepSeek: DeepSeek V4 Flash Vision (Exp)2026-08-21$0.22 / $0.66 per 1M tokens · 220 tok/s
- z-aiZ.ai: GLM 5.32026-08-1845Intelligence75Coding
- obsidianQwen3.8 27B2026-08-1534Intelligence68Coding
- deepseekDeepSeek: DeepSeek V4 Pro 08132026-08-1236Intelligence69Coding
- grokSpaceXAI: Grok 4.62026-08-1244Intelligence77Coding
- metaMeta: Muse Spark 1.22026-08-0540Intelligence72Coding
Gemini 3.8 Live and Gemini 3.8 Live Extended Thinking shipped on September 15, 2026 — the two native live-dialogue endpoints Google opened on the vendor's API, one optimised for latency and one for deliberation. On September 24 the company announced Gemini 3.8 Live with Live Avatar, which pairs near real-time video generation with the same speech loop so the model has a face while it talks. Nothing about the two model IDs changed. What changed is what the conversation is allowed to look like, and — more consequentially — what the model is allowed to do to the conversation while it is still running.
What actually shipped on 24 September
The DeepMind post is short and specific, and it is worth separating what it claims from what it means. Live Avatar, in Google's own words, "brings near real-time visual presence to Gemini's conversational AI" by pairing real-time video generation with the existing speech stack. The company describes precise lip-syncing, natural expressions and fluid turn-taking, and gives two deployment examples: customer service and interactive walkthroughs. Then it says the sentence that matters most for anyone planning a build — "Starting today, Gemini 3.8 Live with Live Avatar is available in Gemini Enterprise."
That is the whole availability story. Live Avatar is not a Gemini API model ID. The API's audio model list still contains gemini-3.8-live and gemini-3.8-live-extended-thinking and no avatar row, and the rate card has no avatar line item. The feature lands inside Gemini Enterprise, which means the audience for the announcement is enterprise buyers and the developers who integrate on their behalf, not the individual developer calling the Live API with a key today.
Two of the post's claims are worth quoting precisely, because both are stronger than the usual launch language. The first: Live Avatar "features native multilingual speech-to-speech synchronization" and "can seamlessly transition across 97 languages without degrading video fidelity or introducing visual drift." The 97 figure is the same language count the September 15 launch claimed for the underlying live-dialogue models, so this is the existing multilingual claim restated with a new constraint attached — the lip-sync and the facial animation have to keep up when the language changes mid-sentence. The second: all output is watermarked with SynthID, "woven directly into the audio and video output." Both tracks, not just the voice.
The genuinely new capability is the one in the middle
Read past the visuals and the most interesting paragraph is the one about tool calls. Google says Live Avatar is backed by "asynchronous tool calling" that can "trigger tool calls and fetch data in the background while continuing active dialogue, handling complex tasks while ensuring an uninterrupted conversational flow." The worked example is a hotel guest check-in where the model calls tools in the background and keeps talking.
That is a real architectural difference from the request-response shape most voice integrations are built around, and it is the part with a cost attached. Asynchronous execution means the model is doing work the transcript does not show. In a text pipeline you would see the tool call as a turn. Here it happens underneath a conversation that is still in progress, which raises the same questions any concurrent execution raises: what happens if the tool call fails silently mid-sentence, and how does the caller know? Google's post does not say, and the model card is the place to look for it. Treat the "uninterrupted conversational flow" claim as vendor-reported and untested by any third party we can find.
Preset avatars, and the allowlist that limits the interesting half
The customisation story has two tiers and only one of them is generally available. Every enterprise deployment gets "a library of diverse, preset avatars." Custom avatars — generated "from a high-quality reference image" while "preserving reference likeness, brand styling, or character identity" — are behind a gate, and Google states it plainly: "Custom avatar creation is currently available only through enterprise allowlisting."
So the capability most teams will actually want, the one that lets an avatar match a brand or a named character, is the one you cannot self-serve. If your plan depends on a synthetic presenter who looks like your mascot, you are waiting on an allowlist decision and not on a model release. That is a procurement fact, not a technical one, and it is the kind of thing that quietly slips a quarter.

Where it sits against the rest of the line
Live Avatar did not arrive into an empty product family, and the position it occupies is easiest to see against the siblings that shipped in the same fortnight.
• Ships as — Gemini 3.8 Live with Live Avatar is an enterprise capability inside Gemini Enterprise vs Gemini 3.8 Live and Gemini 3.8 Live Extended Thinking are Gemini API endpoints with model IDs and published per-minute rates
• Callable by developers — Live Avatar no, no model ID and no rate-card line vs the two Live endpoints yes, gemini-3.8-live and gemini-3.8-live-extended-thinking
• Output — Live Avatar audio plus synchronised video vs the Live endpoints audio only
• Language claim — Live Avatar 97 languages with lip-sync and expression continuity vs the Live endpoints 97 languages with automatic mid-conversation switching
• Watermark — Live Avatar SynthID on both the audio and the video track vs the Live endpoints SynthID on generated audio
The two Live endpoints themselves are the well-documented pair. Independent measurement has them far apart on some axes and close on others: on the Artificial Analysis Speech to Speech Index, Gemini 3.8 Live Extended Thinking (High) sits at 82.6 against Gemini 3.8 Live at 76.0, a gap built mostly on reasoning quality rather than conversational dynamics, where the ordering flips. Google's own figures have them at 68.6% and 30.1% on τ-Voice task completion and 98% and 92% on Big Bench Audio. Live Avatar inherits whichever of those you call underneath it, and inherits their pricing too, because the avatar is a presentation layer over the same conversation loop.

What this does not change
It does not make the models better. Live Avatar is a presentation and orchestration layer: the quality numbers for Gemini 3.8 Live are what they were on September 15, and anyone who needs the stronger of the two variants still has to choose Extended Thinking and accept its latency. It does not put video in the API. And it does not change the price of talking to the model, which is still billed on the Live API's per-minute audio rates — $0.005 per minute of audio in and $0.018 per minute of audio out — with the avatar's video generation unpriced in public because it is not sold separately.
What it does change is the set of products that can be built without a separate rendering layer. A support agent that previously spoke and left a blank panel on screen can now hold a face while it works, and the work it is doing in the background is no longer visible as dead air. That is a meaningful change to the shape of an interface and a modest change to the underlying model. Both of those can be true at once.

What to watch, and one routing note
Three things would move this from an announcement to a build decision. Custom avatar allowlisting would have to open up, because preset avatars are a demo and custom avatars are a product. The video track would have to get a price, because nobody can model unit economics on an unpriced output. And an avatar endpoint would have to appear in the API's model list, because that is the difference between an enterprise feature and something a developer can call tonight.
On our own side, one thing is worth stating precisely, since it is easy to assume otherwise: OrcaRouter does not route the Gemini 3.8 Live endpoints or Live Avatar, and nothing here should be read as a claim that it does. What we do carry is the rest of Google's 3.8 line — google/gemini-3.8-flash among them — alongside a catalogue of more than 200 models from a single key at provider list price with no markup. If Live Avatar sends your architecture toward an agent that has to reason about what the customer said, the reasoning half of that stack is the half you can consolidate today.
