Skip to main content
SLNG gives you access to a range of text-to-speech models from multiple providers through a single platform. The execution layer assembles output from cache when possible, so repeated phrases return from the edge without hitting the upstream model. For the full, current list with latency, hosting, and language details, see Text-to-Speech Models. For voice samples, see Voices.

Which approach should you use?

Which model should you use?

Execution layer behavior

Every TTS request goes through the output assembly stage, which checks whether this text, voice, and config combination has been assembled before:
  • Cache hit: audio returns from the edge. No upstream model call. No provider billing.
  • Cache miss: the request routes to the model endpoint, audio is synthesized, and the result is cached.
The more calls flow through the system, the more cache coverage grows. Repeated phrases (greetings, disclosures, confirmations) become effectively free. See Output Assembly for caching, segment reuse, and cache scoping.

Quick example

See HTTP for complete examples in cURL, JavaScript, and Python, and WebSocket Streaming for real-time voice agent audio.