Gemini TTS caps 200 voices per project: picking a voice on Sume

Gemini TTS stores at most 200 voices per project for a year. On Sume you list avatars and use one whose voice.status is ready, with no stored-voice quota.

4 min readSume
All posts

Gemini's speech docs allow at most 200 stored voices per project, each with a 1-year TTL. Sume's docs state no such quota. You choose a voice by listing your avatars and calling TTS with one whose voice.status is ready.

Read 2026-10-01 from the Gemini speech page and the Sume OpenAPI description of the TTS request.

What does the 200-voice cap mean in practice?

It applies to stateful voice_ ids. Once a project holds 200, you prune before adding, and each id lapses after a year. Stateless keys sidestep the count but last 7 days and live in your client.

How do I pick a voice on Sume?

List the workspace avatars, look for voice.status equal to ready, then pass that avatar to POST /v1/tts-1.0/generate. The schema calls the avatar reference the discoverable selector.

curl https://api.sume.com/v1/avatar-1.0/avatars \
  -H "Authorization: Bearer $SUME_API_KEY"

Which request fields select a voice?

Voice selectors on Sume TTS 1.0, OpenAPI schema, read 2026-10-01.
FieldWhat it takes
avatar_idWorkspace avatar id from the avatar list
avatar_handleAvatar handle
voice.idVoice UUID or library id
voice.modeOnly id is supported

Do I need a registry of voices in my app?

Not for quota reasons. Keep a cache of avatar ids you use often, and refresh it from the list when a call fails. If you are porting from Gemini, swap the pruning job for one list call. For the id format see Sume voice ids vs Gemini voice design.

Sources

Related posts

More in Developers

All Developers posts

Written by Sume