ElevenLabs product list vs Sume API routes: what has no equivalent

Sume covers text to speech, speech to text, music and word timings in its API, but it has no route for dubbing, voice isolation, sound effects, a voice changer or voice cloning. If your ElevenLabs integration depends on any of those, Sume does not replace it today.

The ElevenLabs list is from its documentation overview, read 2026-10-10, which names text to speech, speech to text, music, text to dialogue, image and video, voice changer, voice isolator, dubbing, sound effects, voice cloning and design, remixing, forced alignment and agents. The Sume side is from the OpenAPI document published with the docs, where I listed every path, plus the Timeline audio and Music Router pages.

Matching the list to Sume's routes

I checked each ElevenLabs capability against the paths in Sume's OpenAPI file. A match means a route exists for the same kind of work, not that the output is equal. Quality, languages and voices are things to test yourself.

Close calls

Two rows look like matches and are not. /v1/audio-detach pulls the audio track out of a video file; it does not clean speech. The TTS timestamps are word timings for audio Sume generates, so they are not an alignment service for arbitrary audio you bring. For arbitrary audio, STT 1.0 gives you words[] with start and end times, which covers many alignment needs, but it is transcription, not alignment of a known script.

Dubbing is the largest gap. You can assemble a rough equivalent from STT, a translation step you supply, TTS and Timeline, but that is a pipeline you maintain, with no lip-sync or voice matching from Sume. An ElevenLabs dubbing call is one request.

Where Sume fits instead

The reason to use Sume for audio is proximity to the rest of a video job. The same key and the same job envelope cover TTS, music, avatar video, Timeline renders and captions, and a Timeline can take a TTS result as its audio spine. If your product only needs a voice or a sound-effects library, a specialist audio vendor will serve you better, and this post is not a reason to move.

Before you decide, list the ElevenLabs calls your code makes today and mark each against the table. If all of them have a route on the Sume side, run a small test of your real scripts. If one has none, keep that one where it is and move only the rest.