Loading the catalogue…
Loading the catalogue…
OpenAI GPT-4o Mini TTS snapshot (2025-03-20): text-to-speech on the audio API, 2K input tokens, deprecated with 2027-01-06 shutdown.
Overview. gpt-4o-mini-tts-2025-03-20 is OpenAI’s March 20, 2025 snapshot of a text-to-speech model built on GPT-4o Mini. It takes text input and returns audio on the speech endpoint, not chat or realtime APIs. Developers reach for it when they need compact prompt-to-speech synthesis rather than a general-purpose language model.
Key strengths. The model is purpose-built for speech synthesis: text in, audio out, with streaming playback suited to on-demand spoken responses. Documented uses include narration, multilingual spoken audio, and realtime audio output. Optional audio streaming lets callers start playback without waiting for a full render on the speech API.
When to use it. Use this snapshot for simple text-to-speech jobs when you need spoken output of short prompts and do not need chat, tools, or multi-step reasoning. It fits interactive product flows—notifications, read-aloud helpers, lightweight voice UX—where input stays within a few thousand tokens. Prefer it only while the snapshot remains available and migration off deprecated speech APIs is still staged.
Limitations. Input is capped at 2,000 tokens, far below typical chat context windows, and output is audio only with no text completion, tool calling, or structured output path. The speech endpoint does accept an instructions string for steering voice style, but not a Chat Completions system message. OpenAI has deprecated this snapshot for API shutdown on January 6, 2027, pointing callers toward gpt-realtime-2.1-mini. It is not a Chat Completions, Responses, or Realtime model.
Sovereignty note. OpenAI is a U.S. creator, so hosted inference carries CLOUD Act exposure and is not Sovereign. Closed proprietary weights, a U.S. default endpoint, and only an eligible-customer option to process API data in Europe make this a poor fit for regulated workloads that require guaranteed EU data residency or sensitivity-safe routing.
| Inference Provider | Sovereignty | Runs in | Price | Status | Pin |
|---|---|---|---|---|---|
| L0 | €0.54 per 1M input tokens€10.77 per 1M output tokens | Online |
14 use cases classified by the curator. The note says why.
Model identity is explicitly the gpt-4o-mini TTS variant with active status and 128K context, making it a direct production fit for text-to-speech workloads in the cost-efficient mini tier.
Dedicated TTS endpoint in the gpt-4o-mini family supplies the synthesis leg required for voice agents; 128K context supports longer spoken turns without immediate truncation.
Can serve the spoken-output path of voice-enabled support bots via native TTS, though it is not a general chat instruct model and no tool-calling is flagged.
Viable for the spoken delivery layer of sales assistants where gpt-4o-mini-tier cost and 128K context matter, but not for underlying reasoning or CRM tool use.
Lacks tool-calling and agentic coding signals; speech-synthesis role conflicts with repository-scale coding agents.
No tool-calling, computer-use, or agentic flags; architecture is speech synthesis, not browser control.
TTS endpoint with no code-oriented benchmarks or instruct tooling flagged; unsuitable as a default code-review model.
No vision/OCR capability; model is text-to-speech only.
No function-calling or tool-use capability is flagged on this TTS-specific variant.
No vision capability flagged; pure audio-synthesis variant cannot ingest or answer over images.
Sourced numbers, not our own evaluations. Percentiles are against the speech models on Stav.
No benchmark source yet
curl https://api.stav.ai/v1/audio/speech \
-H "Authorization: Bearer $STAV_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model": "openai/gpt-4o-mini-tts-2025-03-20", "input": "Hei, verden!", "voice": "alloy"}' \
--output speech.mp3→ X-Stav-Request-Id · X-Stav-Model · X-Stav-Provider → X-Stav-Sovereignty-Level — the rung the request was served at