Skip to main content
Using a coding agent? Install the together-audio skill to let your agent write correct text-to-speech code automatically. See agent skills for details.
Together AI hosts text-to-speech models with multiple delivery methods. Use this page for the basics: making a request, picking a model, and configuring parameters. For real-time delivery, see Streaming and WebSocket.
Read the end-to-end guide to build a live voice agent powered by Together AI’s real-time STT and TTS pipeline.

Quickstart

Basic text-to-speech request:
Outputs a speech.mp3 file.

Available models

For the current list of text-to-speech models, see the serverless catalog or the dedicated model inference catalog.

Parameters

Word alignment (alignment=word) is only supported for streaming requests.
For the full set of parameters refer to the API reference for /audio/speech.

Response formats

Together AI supports multiple audio formats:

Best practices

Choose the right delivery method

  • Basic HTTP API: Best for batch processing or when you need complete audio files.
  • Streaming HTTP API: Best for real-time applications where TTFB matters. See Streaming.
  • WebSocket API: Best for interactive applications requiring lowest latency (chatbots, live assistants). See WebSocket.

Performance tips

  • Use streaming when you need the fastest time-to-first-byte.
  • Use the WebSocket API for conversational applications.
  • Buffer text appropriately. Sentence boundaries work best for natural speech.
  • Use the max_partial_length parameter in WebSocket to control buffer behavior.
  • Consider using raw (PCM) format for lowest latency, then encode client-side if needed.

Voice selection

  • Test different voices to find the best match for your application.
  • Some voices are better suited for specific content types (narration vs conversation).
  • Use the Voices API to discover all available options.

Supported voices

Some of the supported voices for each model are shown below. For the full list of available voices, query the /v1/voices endpoint.

Voices API

Available voices

Orpheus model

Sample voices include:
Text

Kokoro model

Text
Voice mixing (Kokoro only)
Kokoro supports combining two or more voices into a single blended voice by joining their names with +. This can be useful for creating custom voice characteristics that aren’t available from any single voice on its own.
  • Equal weights: af_bella+af_heart blends the two voices in equal proportion.
  • Custom weights: af_bella(2)+af_heart(1) weights af_bella twice as heavily as af_heart. Weights can be integers or decimals.
  • More than two voices: af_bella(1)+af_heart(1)+am_adam(0.5). Any number of components is supported.
Voice mixing is only supported for hexgrad/Kokoro-82M. Other TTS models require a single voice name.
Example:
cURL

Cartesia models

All valid voices supported by Cartesia are supported.
You need to pass in the voice ID instead of the name. Model strings are deprecated and will not be supported in future.

Rime Mist v2, v3 models

Text

Rime Arcana v2, v3, and v3 Turbo models

Rime Arcana v3 and Arcana v3 Turbo are multilingual models.
Text

Minimax Speech 2.6 Turbo model

Sample voices include:
Text

Minimax Speech 2.8 Turbo model

Sample voices include:
Text

Pricing

Next steps

  • Streaming: stream audio over HTTP for low time-to-first-byte, plus how to extract raw PCM bytes.
  • WebSocket API: stream text in and audio out over a single WebSocket for the lowest interactive latency, including multi-context support.
  • API reference for detailed parameter documentation.
  • Speech-to-text for the reverse operation.
  • PDF to Podcast guide for a complete example.