GPT Realtime Translate
OpenAI realtimeGPT Realtime Translate is an OpenAI realtime audio model.It supports a 16,000-token context windowwith up to 2,000 output tokens. Capabilities include audio input. Route GPT Realtime Translate via Future AGI's Agent Command Center for unified observability, caching, and 15 routing strategies including cost-optimized fallback.
We don't have verified per-token pricing for GPT Realtime Translate yet. If you have a source from OpenAI's documentation, help us add it — your submission gets reviewed within 48 hours.
Pricing
Per-token rates, expressed in USD per 1M tokens. Verified Oct 22, 2026.
| Input | — | |
| Output | — |
Context & limits
- Context window
- 16,000 tokens
- Max input
- 16,000 tokens
- Max output
- 2,000 tokens
- Modalities
- audio_in, audio_out, text
Capabilities
- Function calling — not advertised
- Parallel tool calls — not advertised
- Vision input — not advertised
- Audio input ✓ supported
- Audio output ✓ supported
- PDF input — not advertised
- Streaming ✓ supported
- Structured output — not advertised
- Prompt caching — not advertised
- Reasoning — not advertised
Strengths & caveats — when to pick GPT Realtime Translate
Data-driven from GPT Realtime Translate's percentile within realtime peers.
Where it's strong
- +voice agents and audio Q&A
Watch out for
- !limited context — 16,000-token window is in the bottom quartile; not ideal for long documents or large RAG
Benchmarks pending
We haven't logged public benchmark scores for GPT Realtime Translate yet. Have one to contribute? Submit a source — citations help us prioritise.
Call GPT Realtime Translate via Agent Command Center
One OpenAI-compatible endpoint. Routing, fallback, semantic caching, guardrails, and cost tracking come along for the ride. First 100K requests + 100K cache hits free every month.
agentcc / @agentcc/client). Per-call metadata — provider, cost, latency, cache hit, request id — is returned on x-agentcc-* response headers, so any HTTP client can read it.# GPT Realtime Translate via the Agent Command Center Python SDK
# pip install agentcc
import os
from agentcc import AgentCC
client = AgentCC(
api_key=os.environ["AGENTCC_API_KEY"], # from app.futureagi.com → Settings → API Keys
base_url="https://gateway.futureagi.com/v1",
)
resp = client.chat.completions.create(
model="openai/gpt-realtime-translate",
messages=[{"role": "user", "content": "Hello, GPT Realtime Translate!"}],
)
print(resp.choices[0].message.content)
print(f"Tokens: {resp.usage.total_tokens}")
# Per-call gateway metadata is returned on x-agentcc-* response headers.
# When you need it programmatically, use .with_raw_response to get them:
raw = client.chat.completions.with_raw_response.create(
model="openai/gpt-realtime-translate",
messages=[{"role": "user", "content": "Same call, but I want the headers."}],
)
print("Provider:", raw.headers.get("x-agentcc-provider"))
print("Latency:", raw.headers.get("x-agentcc-latency-ms"), "ms")
print("Cost: ", raw.headers.get("x-agentcc-cost"), "USD")
print("Cache: ", raw.headers.get("x-agentcc-cache"))AGENTCC_API_KEY with a key fromapp.futureagi.com.Gateway docs ↗Same model on other providers
gpt-realtime-translate is also available via 1 other route. Pricing, regions, and capabilities can differ — compare before routing production traffic.
| Provider | Input / 1M | Output / 1M | Verified |
|---|---|---|---|
| Azure OpenAI | — | — | Oct 22, 2026 |
Explore similar models
GPT Realtime Translate doesn't have a public Arena ELO score yet, so we group by provider only — quality-tier comparisons need a benchmark. Side-by-side links appear where a comparison page exists; otherwise, open the model profile.
- GPT Realtime mini (2025-12-15)OpenAI · $0.600/M in · $2.40/M out · 128,000 ctxView model →
- GPT Realtime (2025-08-28)OpenAI · $4.00/M in · $16.00/M out · 32,000 ctxView model →
- GPT-4o Realtime (2025-06-03)OpenAI · $5.00/M in · $20.00/M out · 128,000 ctxView model →
- GPT-4o mini Realtime preview (2024-12-17)OpenAI · $0.600/M in · $2.40/M out · 128,000 ctxView model →
FAQ
How much does GPT Realtime Translate cost?
Public per-token pricing for GPT Realtime Translate is not yet published. Submit a source on this page to help us add it.
What is the context window of GPT Realtime Translate?
GPT Realtime Translate supports a 16,000-token context window with up to 2,000 output tokens.
Does GPT Realtime Translate support function calling?
GPT Realtime Translate does not currently advertise function-calling support. For agentic workloads, prefer a tool-calling-capable model and route via Agent Command Center for fallback.
Is GPT Realtime Translate good for production?
GPT Realtime Translate is well-suited for voice agents and audio Q&A. Consider alternatives if you need limited context — 16,000-token window is in the bottom quartile; not ideal for long documents or large RAG.
How can I route to GPT Realtime Translate with fallback?
Use Agent Command Center: a single OpenAI-compatible endpoint that supports cost-optimized routing, latency-aware retries, model fallback, and shadow traffic. Configure once, swap models without app changes.
Useful links for GPT Realtime Translate
Official sources, independent benchmarks, and pricing aggregators — no random search-engine guesses.
Third-party evals — verify the marketing.
Cross-check our number against the rest of the ecosystem.