Successful inference trendActivity
Flatkey price
Live catalog modelInput /M
$1.6
Input /M
$1.6$2
Cache /M
$0.16$0.2
Output /M
$9.6$12
gpt-5.6-terra API
OpenAI gpt-5.6-terra for chat and coding; Flatkey routes this model through /v1/chat/completions. $1.6/$9.6 per 1M tokens 1,048,576-token context window.
Input /M
Reference price: $2
$1.6-20%
Cache /M
Reference price: $0.2
$0.16-20%
Output /M
Reference price: $12
$9.6-20%
Provider
OpenAI
gpt-5.6-terra API performance
gpt-5.6-terra API reliability and uptime
Live Flatkey request telemetry for gpt-5.6-terra appears here when enough production traffic is available.
Avg. provider uptime
92.2%
last 30 days
Latency
2.52s
last 30 days
Requests
167K
30-day window
Successful inference trend
#4 · 1.84T
gpt-5.6-terra API activity
gpt-5.6-terra API usage and request activity
Track request volume and successful inference activity for gpt-5.6-terra over the latest reporting window.
Requests
167K
30-day window
Latency
2.52s
last 30 days
Uptime
92.2%
last 30 days
gpt-5.6-terra pricing
gpt-5.6-terra API pricing and billing
Prices below are calculated from Flatkey pricing data for this model and the visible groups currently returned by our pricing API.
View API
Shared balance
Add credits Add credits
Use the same Flatkey balance and API key across image, video, audio, and text models.
Model catalog
- Model Type
- Text
- API
- /v1/chat/completions
- Billing basis
- 1M tokens
gpt-5.6-terra chat and coding: core capabilities
OpenAI's gpt-5.6-terra route supports text · image · file. Catalog categories: Programming, Marketing, SEO.
gpt-5.6-terra chat and coding API
Call gpt-5.6-terra through /v1/chat/completions for chat, coding or agent workflows supported by the model's listed modalities.
gpt-5.6-terra long-context work
gpt-5.6-terra is listed with 1,048,576-token; use that catalog value as an integration planning reference and validate limits for your account.
gpt-5.6-terra tool and agent workflows
Keep tool calls, structured output and streaming behavior aligned with the endpoint contract instead of assuming every provider feature is interchangeable.
gpt-5.6-terra production routing
Use one Flatkey key for gpt-5.6-terra, usage controls and model routing while retaining the exact model id in your SDK configuration.
Compare
gpt-5.6-terra API comparison: capabilities and access
Compare the catalog facts for gpt-5.6-terra with the previous-generation baseline before changing your integration.
| Capability | Previous generation | gpt-5.6-terra |
|---|---|---|
| Provider | Not verified in this catalog snapshot | OpenAI |
| Modalities | Not verified in this catalog snapshot | text · image · file |
| Context | Not verified in this catalog snapshot | 1,048,576-token |
| Endpoint | Not verified in this catalog snapshot | /v1/chat/completions |
| Billing | Not verified in this catalog snapshot | $1.6/$9.6 per 1M tokens |
Why Flatkey
Why use Flatkey for gpt-5.6-terra?
OpenAI-compatible migration path
Chat Completions-style payloads reduce switching friction from existing model stacks.
Production routing
Keep usage, keys, quotas, and model routing in one Flatkey account.
Unified API access
Use one account and API key across image, video, audio, and language models.
Routing across upstream channels
Requests are spread across the channels serving this model, with 30-day uptime published above.
API Gateway
Supported endpoint coverage in our pricing API.
Call this model through the same OpenAI-compatible router and API key as the rest of the Flatkey catalog.
Use your existing SDK and set its base URL to the Flatkey router origin.
Keep prompts and request files in your terminal workflow with the Flatkey CLI.
Use the same key with your coding agent and route model jobs from a script.
curl https://router.flatkey.ai/v1/chat/completions \ -H "Content-Type: application/json" \ -H "Authorization: Bearer sk-..." \ -d '{ "model": "gpt-5.6-terra", "messages": [ { "role": "user", "content": "You are a senior backend engineer. In 3 sentences, explain why developers should use an LLM gateway instead of calling each official API directly." } ] }'
FAQ
gpt-5.6-terra API
pricing, features, and usage FAQs
Answers about gpt-5.6-terra pricing, capabilities, endpoint access and catalog limits.
What is gpt-5.6-terra used for?
gpt-5.6-terra is listed by OpenAI for chat and coding; the catalog lists these modalities: text · image · file.
How is gpt-5.6-terra priced?
Use the pricing section above for current Flatkey prices from our pricing API.
Which API endpoint calls gpt-5.6-terra?
Flatkey routes this model through /v1/chat/completions. Set the model field to gpt-5.6-terra and follow the fields supported by that endpoint.
What context or input limits does gpt-5.6-terra have?
gpt-5.6-terra is listed with 1,048,576-token. Other limits depend on the route and current account availability, so verify them before production use.