OpenAI · Audio

gpt-4o-mini-tts API

gpt-4o-mini-tts from OpenAI is an audio service in the catalogue. Text to speech and speech recognition are different tasks; confirm the model’s task and supported audio format before integrating.

Preparing

Service type

Sale prices will appear after provider configuration is complete.

API model ID
gapgpt-gpt-4o-mini-tts-5180ac2482
Model developer
OpenAI
Service type
Audio
Current availability
Preparing

Model features

No additional gateway capabilities have been confirmed for this model.

What is gpt-4o-mini-tts?

Use the public identifier gapgpt-gpt-4o-mini-tts-5180ac2482 for gpt-4o-mini-tts in ServerNet. The gateway uses this identifier to select the configured route; the developer is OpenAI.

For gpt-4o-mini-tts, use the listed model ID and endpoint instead of assuming every GPT parameter is supported. Compare both input and output prices for your expected request size.

Where to use gpt-4o-mini-tts

  • Check whether gpt-4o-mini-tts synthesizes speech or transcribes audio.
  • Evaluate pronunciation or transcription quality with a representative sample.
  • Check audio duration, output format and supported voices or languages for your application.

Build your integration

Audio execution needs explicit text or file limits and a verified native endpoint. Use the documented route once it becomes available; a text chat request does not perform an audio task.

Inputs and service limits

Character, duration and generation limits differ between audio models. Voice conditioning and uploaded audio can add consumption. Supported languages and voices must come from the model’s confirmed contract.

Image, audio, video and other native services can use different billing units. A token tariff is not a valid substitute. Sale opens only after the execution path and bounded billing contract are verified.

Frequently asked questions

Is gpt-4o-mini-tts available through ServerNet?

gpt-4o-mini-tts is currently unavailable for API use. A catalogue listing does not activate billing or access. Choose an available related model or check this page again after the route is verified.

Which model ID and API endpoint should I use for gpt-4o-mini-tts?

This model needs a native execution route. A chat, embedding or reranking example would not execute the advertised task. Its public page remains a catalogue reference until the route and metering are ready.

How is gpt-4o-mini-tts usage charged?

Image, audio, video and other native services can use different billing units. A token tariff is not a valid substitute. Sale opens only after the execution path and bounded billing contract are verified.

What should I check before using gpt-4o-mini-tts in production?

Character, duration and generation limits differ between audio models. Voice conditioning and uploaded audio can add consumption. Supported languages and voices must come from the model’s confirmed contract.

Compare models for the same task

Audio8

Audio8-TTS-Preview-0.6b

Available Audio
Unit rate ceiling, IRT1,426
1000 Input characters · The final usage amount follows the reported result and the permitted request options.
ResembleAI

chatterbox-multilingual

Available Audio
Unit rate ceiling, IRT286
1000 Input characters · The final usage amount follows the reported result and the permitted request options.
ResembleAI

chatterbox-turbo

Available Audio
Unit rate ceiling, IRT286
1000 Input characters · The final usage amount follows the reported result and the permitted request options.
sesame

csm-1b

Available Audio
Unit rate ceiling, IRT1,997
1000 Input characters · The final usage amount follows the reported result and the permitted request options.
bosonai

HiggsAudioV2.5

Available Audio
Unit rate ceiling, IRT5,703
1000 Input characters · The final usage amount follows the reported result and the permitted request options.
hexgrad

Kokoro-82M

Available Audio
Unit rate ceiling, IRT283
1000 Input characters · The final usage amount follows the reported result and the permitted request options.
Only available models are exposed by the API. Availability requires a configured provider, valid prices and a supported execution path.