Model detail
GPT-Audio Mini
A lower-cost GPT-Audio variant supporting audio input and output for audio-enabled conversational applications.
Model specs
- Model ID
-
gpt-audio-mini
- Context length
- 128K
- Max output
- 16.384K
- I/O modalities
- Released
- 2025-10
02
API endpoints
One MixRoute gateway, OpenAI-compatible
-
OpenAI-compatible
/v1/chat/completionsPOST
03
Pricing
Flat rate, unit: /1M Tokens
Input
$75.0000 /1M Tokens
Completion
$150.0000 /1M Tokens
05
Selection summary
Quickly judge whether it fits your workload
What is this model good for?
A lower-cost GPT-Audio variant supporting audio input
A lower-cost GPT-Audio variant supporting audio input and output for audio-enabled conversational applications.
What should you check before using it?
Confirm audio formats, sample rates, and pricing
GPT-Audio Mini supports tool calling, streaming and the OpenAI SDK. Knowledge cutoff: 2023-10-01. Released 2025-10-06. It is billed at 10.00 USD per 1M tokens. Test a representative workload before production.
Why use it through MixRoute?
Swap the base URL, keep the GPT-Audio Mini client
MixRoute serves GPT-Audio Mini on the OpenAI-compatible endpoint /v1/chat/completions; point your existing client at https://api.mixroute.ai/v1 with the model ID gpt-audio-mini and re-run your integration tests.
07
Capabilities & compatibility
Unconfirmed capabilities stay "Unknown," no guesses
Tool calling
GPT-Audio Mini supports function and tool calls.
tools definition; the response returns tool_calls to execute and feed results back.
Streaming
GPT-Audio Mini supports streamed responses.
stream: true streams tokens incrementally, so chat UIs render as they arrive.
OpenAI SDK
Call GPT-Audio Mini through MixRoute's OpenAI-compatible endpoint.
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
For gpt-audio-mini, 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.
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.