Hi Google Gemini team,
I’m experiencing an issue accessing Gemini 3.8 Flash TTS (gemini-3.8-flash-tts) through the Gemini API, despite the model being available and working correctly in Google AI Studio.
Environment:
-
Model:
gemini-3.8-flash-tts -
Voice: Bodi
-
SDK:
google-genai3.1.0 (Python) -
Billing: Tier 1 (paid, prepaid)
-
API key: Created November 11, 2026, through Google AI Studio
-
API restrictions: Gemini API (
generativelanguage.googleapis.com)
What works:
-
I can successfully generate speech using Gemini 3.8 Flash TTS with the Bodi voice inside Google AI Studio.
-
The model appears in my project’s rate-limit dashboard, with an allocation of 10 RPM, 10,000 TPM, and 100 RPD.
-
My API key is active and correctly restricted to the Gemini API.
What fails:
I’ve tested both API interfaces:
-
client.models.generate_content_stream() -
client.interactions.create()
Both return the same error:
404 NOT_FOUND
Model 'gemini-3.8-flash-tts' not found.
Please verify the model name against the supported list:
https://ai.google.dev/gemini-api/docs/models
Additionally, calling client.models.list() and filtering for model names containing tts returns no results.
I’ve verified that the API key belongs to the intended Google Cloud project and that the Gemini API restriction is configured correctly.
Expected behavior:
The API should recognize gemini-3.8-flash-tts and allow speech generation using Bodi, consistent with the model availability shown in Google AI Studio and the official documentation.
Questions:
-
Is Gemini 3.8 Flash TTS currently accessible through the public Gemini API for Tier 1 projects?
-
Is there a difference between model availability in AI Studio’s speech-generation interface and availability through API keys?
-
Does this model require additional activation, a particular API version, or a different endpoint?
-
Is there a known issue causing this model to return 404 despite appearing in the project’s rate-limit dashboard?
I’m developing an automated long-form narration workflow and would appreciate clarification on the correct API configuration.
Thank you!
