One narrator across a series: Sume TTS 1.0 is Sonic 3.6, pin older ids

Sume TTS 1.0 always runs on sonic-3.6. To keep a series that began on an older Sonic, use the TTS Router and pin sonic-3.5 or sonic-3 with the same voice.

5 min readSume
All posts

POST /v1/tts-1.0/generate has no engine picker and always runs on sonic-3.6, the current stable Sonic. If a series began on an older engine and you want episode twelve to sound like episode one, call POST /v1/tts-router/generate with a required model such as sonic-3.5 or sonic-3 and the same voice. Sending model to TTS 1.0 is a 400.

The catalog is read from the Sume TTS router API (GET /v1/tts-router/models) described in the Sume API reference (read 2026-10-06).

Which ids can I pin?

The router's v1 catalog has five ids, all Cartesia Sonic.

TTS Router model ids (read 2026-10-06)
IdWhat it is
sonic-3.6Current stable Sonic; what TTS 1.0 uses
sonic-3.5Earlier Sonic release
sonic-3Earlier Sonic release
sonic-latestAlias that resolves to sonic-3.6, never the preview
sonic-previewBeta channel; can change without notice and rejects pro voice clones

How do I keep the voice the same?

The router uses the same voice selectors as TTS 1.0: avatar_id, avatar_handle or voice.id. It does not make a second voice namespace. Pin an exact id in the series config, not sonic-latest, so a future alias move does not change the sound mid-season.

What should I test?

Listen to the same paragraph on sonic-3.5 and sonic-3.6 with your voice before you commit the series. The job.model field on each result records the id you asked for, so you can audit which engine voiced each episode.

Sources

More in Models

All Models posts

Written by Sume