How do you start calling tts-hd?

Use the model ID tts-hd through the compatible text-to-speech endpoint. It produces higher quality audio output than tts.

How does tts-hd compare to tts?

tts-hd offers higher quality audio output than tts. It may have higher latency and cost. Test your text with both to compare.

How should you set the output budget for tts-hd?

For tts-hd, set the max_tokens or max_completion_tokens parameter to control spending per call. Start with a budget aligned to your typical response length and increase only when longer outputs are genuinely needed. Monitor token usage in the API response headers to tune your budget over time.

When was TTS-1 HD released, and is it still maintained?

TTS-1 HD is listed with catalog status stable. The recorded release date is 2023-11-06. Check the model page for deprecation notices before you build a long-lived integration on it.

What voices does tts-hd support?

Confirm the current available voice options in the model documentation. tts-hd is optimized for the highest quality voice output.

Does TTS-1 HD support streaming output?

Yes. TTS-1 HD is declared as supporting streamed responses.

Can you call TTS-1 HD with the OpenAI SDK you already use?

Yes. TTS-1 HD is reachable through an OpenAI-compatible endpoint, so an existing OpenAI SDK client works after pointing the base URL at MixRoute and setting the model parameter to tts-hd . Keep your current request and response handling.

Model detail

TTS-1 HD

Provided by OpenAI

Pay-as-you-go

The higher-quality member of OpenAI's TTS family focuses on converting written text into natural-sounding spoken audio.

Model specs

Model ID: tts-hd

Context length: –
Max output: –
I/O modalities
Released: 2023-11

API endpoints

One MixRoute gateway, OpenAI-compatible

OpenAI-compatible /v1/chat/completions POST

Pricing

Flat rate, unit: /1M Tokens

Input

$75.0000 /1M Tokens

Completion

$75.0000 /1M Tokens

Selection summary

Quickly judge whether it fits your workload

What is this model good for?

The higher-quality member of OpenAI's TTS family focuses on converting written text

The higher-quality member of OpenAI's TTS family focuses on converting written text into natural-sounding spoken audio.

What should you check before using it?

Confirm audio formats, sample rates, and pricing

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

Why use it through MixRoute?

Swap the base URL, keep the TTS-1 HD client

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

Capabilities & compatibility

Unconfirmed capabilities stay "Unknown," no guesses

Streaming

TTS-1 HD supports streamed responses.

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

OpenAI SDK

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

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

Token cost estimator

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

Input tokens

Output tokens

Requests / month

Cache hit rate –

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

FAQ

TTS-1 HD is billed per use and the record publishes no free-tier allowance. The current published rates are input $75.0000 per 1M tokens and output $75.0000 per 1M tokens. Trial credit or promotional quota is tied to your account rather than to the model, so check the console before planning around a free tier.

Get started

01

Create an API key

Generate a key in the Console; one key calls every model.
02

Set the base URL

Fully OpenAI SDK-compatible; just swap the URL to connect.

https://api.mixroute.ai/v1
03

Specify the model ID

In the request's model field, enter:

tts-hd

Create an API key

New users get $5 in free credits

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.

Create an API key View integration docs