Skip to content

Model detail

TTS-1

Provided by OpenAI
Pay-as-you-go

OpenAI's TTS model family converts written text into natural-sounding speech for spoken-audio applications.

Model specs

Model ID
tts
Context length
–
Max output
–
I/O modalities
Released
2023-11

02

API endpoints

One MixRoute gateway, OpenAI-compatible

  • OpenAI-compatible /v1/chat/completions POST

03

Pricing

Flat rate, unit: /1M Tokens

Input

$75.0000 /1M Tokens

Completion

$75.0000 /1M Tokens

05

Selection summary

Quickly judge whether it fits your workload

What is this model good for?

OpenAI's TTS model family converts written text into natural-sounding speech

OpenAI's TTS model family converts written text into natural-sounding speech for spoken-audio applications.

What should you check before using it?

Confirm audio formats, sample rates, and pricing

TTS-1 supports streaming and the OpenAI SDK. Released 2023-11-06. It is billed at 15 USD per 1M characters. Test a representative workload before production.

Why use it through MixRoute?

Swap the base URL, keep the TTS-1 client

MixRoute serves TTS-1 on the OpenAI-compatible endpoint /v1/chat/completions; point your existing client at https://api.mixroute.ai/v1 with the model ID tts and re-run your integration tests.

07

Capabilities & compatibility

Unconfirmed capabilities stay "Unknown," no guesses

Available:

Streaming

TTS-1 supports streamed responses.

EX stream: true streams tokens incrementally, so chat UIs render as they arrive.
Available:

OpenAI SDK

Call TTS-1 through MixRoute's OpenAI-compatible endpoint.

EX Change base_url to https://api.mixroute.ai/v1; everything else follows the OpenAI style.

08

Token cost estimator

Live estimate from this page's pricing, not an actual bill

This model has no cache-read price; caching is not counted

09

FAQ

tts is OpenAI’s standard text-to-speech model that converts text to natural-sounding spoken audio. It is suitable for general-purpose voice synthesis.

One endpoint, a testable decision

Test this model and alternate routes with the same request format

Start from a real workload, then let quality, total cost, and failure conditions decide whether to send production traffic.