GPT-5.6 Terra: Complete Specifications, Pricing, API Access & Use Cases (2026)
What Is GPT-5.6 Terra?
GPT-5.6 Terra is OpenAI’s cost-balanced reasoning model, generally released on July 13, 2026, with a 1,050,000-token context window, text and image input, text output, and standard API pricing of \$2.50 per million input tokens and \$15 per million output tokens as of July 2026.
OpenAI describes Terra as the GPT-5.6 model designed to balance intelligence and cost. It occupies the middle position in the GPT-5.6 family, between the flagship GPT-5.6 Sol and the lower-cost GPT-5.6 Luna. OpenAI also states that Terra roughly corresponds to the mini tier used in earlier GPT-5 model families.
The model is intended for coding, professional knowledge work, general reasoning, tool-assisted workflows, and agent orchestration where a team needs more capability than a high-volume economy model but does not require the highest-priced family tier.
GPT-5.6 Terra is available through the OpenAI API. OpenAI also makes it available in Codex and Work in ChatGPT for eligible plans, although it is not selectable in ordinary ChatGPT conversations.
According to the Gate.AI model-card entry, the model is listed under the provider-qualified identifier openai/gpt-5.6-terra.
What Are GPT-5.6 Terra’s Key Specifications and Pricing?
The table below separates model specifications from access-dependent information. Prices are quoted per one million tokens unless otherwise stated.
| Specification | Verified Value |
|---|---|
| Provider | OpenAI (as of July 2026) |
| Model family | GPT-5.6 (as of July 2026) |
| Model type | Proprietary multimodal reasoning model (as of July 2026) |
| General release date | July 13, 2026 (as of July 2026) |
| Context window | 1,050,000 tokens (as of July 2026) |
| Maximum output | 128,000 tokens (as of July 2026) |
| Knowledge cutoff | February 16, 2026 (as of July 2026) |
| Standard input pricing | \$2.50 per 1M tokens (as of July 2026) |
| Standard cached-input pricing | \$0.25 per 1M tokens (as of July 2026) |
| Standard cache-write pricing | \$3.125 per 1M tokens (as of July 2026) |
| Standard output pricing | \$15.00 per 1M tokens (as of July 2026) |
| Long-context input pricing | \$5.00 per 1M tokens for requests above 272K input tokens (as of July 2026) |
| Long-context cached input | \$0.50 per 1M tokens for requests above 272K input tokens (as of July 2026) |
| Long-context cache writes | \$6.25 per 1M tokens for requests above 272K input tokens (as of July 2026) |
| Long-context output pricing | \$22.50 per 1M tokens for requests above 272K input tokens (as of July 2026) |
| Supported input types | Text and images (as of July 2026) |
| Supported output types | Text (as of July 2026) |
| OpenAI API model ID | gpt-5.6-terra (as of July 2026) |
| Gate.AImodel ID | openai/gpt-5.6-terra, as listed on theGate.AImodel card (as of July 2026) |
| OpenAI API access | Responses API and Chat Completions API (as of July 2026) |
| Gate.AIAPI format | OpenAI-compatible API (as of July 2026) |
| Streaming | Supported (as of July 2026) |
| Function calling | Supported (as of July 2026) |
| Structured outputs | Supported (as of July 2026) |
| Fine-tuning | Not supported (as of July 2026) |
| Batch processing | Available through the OpenAI Batch endpoint (as of July 2026) |
| Rate limits | Determined by the OpenAI usage tier; long-context free-tier access is not supported (as of July 2026) |
| Usage restrictions | Subject to OpenAI service terms, platform policies, and applicable law (as of July 2026) |
OpenAI’s model documentation confirms the 1.05M-token context window, 128K maximum output, February 16, 2026 knowledge cutoff, supported modalities, pricing, endpoints, and feature support.
For standard processing, cache writes cost 1.25 times the uncached input price, while cache reads receive a 90% discount. Requests containing more than 272,000 input tokens are billed at twice the standard input rate and 1.5 times the standard output rate for the full request.
These prices describe OpenAI’s published API rates. Gate.AI billing should be checked on the current Gate.AI model card or pricing interface before deployment because gateway pricing, routing conditions, and account-level availability may differ from direct provider pricing.
What Can GPT-5.6 Terra Do That Makes It Useful in Production?
Analyze large codebases and document collections
The 1,050,000-token context window allows applications to submit substantial repositories, technical documentation, logs, contracts, reports, or conversation histories in a single request.
This can reduce the need to divide source material into many small segments. However, a large context window does not guarantee perfect retrieval of every fact, and requests above 272K input tokens enter the higher long-context pricing tier.
Support coding and software-maintenance workflows
GPT-5.6 Terra can assist with code explanation, implementation planning, debugging, test generation, patch preparation, refactoring, and review.
Its Responses API tool support includes hosted shell execution, code interpreter, apply patch, file search, and other development-oriented capabilities. Generated code should still pass repository-specific tests, security review, and human approval before release.
Coordinate tool-using agents
Function calling and structured outputs let applications connect Terra to internal services, databases, search systems, workflow engines, and business APIs.
The model also supports web search, file search, computer use, Model Context Protocol integrations, and tool search through supported OpenAI interfaces. These features are relevant for agents that must gather information, take structured actions, or coordinate multi-step tasks.
Process professional and operational knowledge
Terra may fit research synthesis, technical writing, policy comparison, customer-support analysis, operational reporting, and document transformation.
Its middle-tier positioning can be useful when teams need stronger reasoning than a lightweight model but want lower token costs than GPT-5.6 Sol. Related OpenAI models used for coding and professional knowledge workflows provide useful family context.
Interpret visual information
Image input enables Terra to examine screenshots, charts, diagrams, interface states, scanned pages, and other visual material alongside text prompts.
This makes it relevant for interface analysis, visual question answering, document review, and screenshot-based technical support. The model itself returns text rather than native image, audio, or video output.
What Are GPT-5.6 Terra’s Supported Modalities?
| Modality | Supported? | Notes |
|---|---|---|
| Text input | Yes | Supports prompts, documents, code, and structured text |
| Image input | Yes | Supports visual analysis within model requests |
| Audio input | No | Not supported by GPT-5.6 Terra |
| Video input | No | Not supported by GPT-5.6 Terra |
| Text output | Yes | Native output modality |
| Image output | No native output | A separate image-generation tool can be called through supported workflows |
| Audio output | No | Not supported by GPT-5.6 Terra |
| Video output | No | Not supported by GPT-5.6 Terra |
OpenAI defines Terra as a text-and-image input model with text output. Audio and video are not supported as direct model modalities.
Applications requiring media generation should use specialized models, such as GPT Image 2 for image generation or Sora 2 for video workflows, rather than treating Terra as a native media-generation model.
Where Does GPT-5.6 Terra Fall Short?
Long prompts can become expensive: Terra’s base price is lower than GPT-5.6 Sol, but cost increases materially for very large prompts. Once a request exceeds 272K input tokens, the higher long-context rates apply to the complete request rather than only the tokens above the threshold.
Teams should estimate prompt size, expected output length, cache behavior, and request volume before choosing a long-context architecture.
The knowledge cutoff limits built-in freshness: The model’s documented knowledge cutoff is February 16, 2026. Information published after that date may be absent unless the application supplies current data or enables retrieval tools.
It does not natively generate every media type: Terra accepts images but returns text. Dedicated image, speech, audio, or video generation requires separate tools or models.
Fine-tuning is not supported: OpenAI lists fine-tuning as unsupported for GPT-5.6 Terra. Organizations that require model-weight customization must use prompt design, retrieval, tools, structured workflows, or another model that supports the required optimization method.
Reasoning and tool use can add latency: A reasoning model may take longer than a smaller low-latency model, particularly when it performs multi-step analysis or invokes external tools. Terra may therefore be unnecessarily costly for simple classification, routing, extraction, or templated-response workloads.
Outputs still require validation: GPT-5.6 Terra can produce inaccurate statements, incomplete analysis, insecure code, or incorrect tool decisions.
This is a general AI limitation and is not unique to Terra. Medical, legal, financial, security, employment, and other high-impact outputs require appropriate safeguards, source verification, access controls, and qualified human review.
What Is GPT-5.6 Terra Best Used For?
The phrase "best used for" refers to scenario fit, not universal superiority.
| Use Case | Why GPT-5.6 Terra May Fit | Important Limitation |
|---|---|---|
| Daily software development | Combines reasoning, coding support, long context, and development tools | Code must be tested and reviewed |
| Repository-level analysis | Can process large code and documentation collections | Very large prompts receive higher pricing |
| Agent orchestration | Supports function calling, structured output, MCP, computer use, and tool search | Tool permissions and failure handling must be controlled |
| Technical support | Can analyze text, logs, code, screenshots, and documentation | Troubleshooting conclusions may be incomplete |
| Research synthesis | Can organize and compare large source sets | Current facts require retrieval and source checking |
| Document automation | Useful for transformation, summarization, extraction, and structured drafting | Sensitive documents require privacy and access controls |
| Visual interface analysis | Accepts screenshots and other image inputs | It cannot natively return edited or generated images |
| Repeated long workflows | Prompt caching can reduce the cost of reused context | Cache-write and long-context pricing still apply |
| High-volume simple tasks | May work when additional reasoning is needed | GPT-5.6 Luna or another smaller model may be more economical |
How Does GPT-5.6 Terra Compare to GPT-5.6 Sol and GPT-5.6 Luna?
All three models belong to the GPT-5.6 family but target different cost and capability requirements.
| Comparison Area | GPT-5.6 Terra | GPT-5.6 Sol | GPT-5.6 Luna | Scenario Fit |
|---|---|---|---|---|
| Family position | Balanced middle tier | Flagship tier | Lowest-cost family tier | Choose according to task complexity and budget |
| Standard input price | \$2.50 per 1M | \$5.00 per 1M | \$1.00 per 1M | Terra sits between Sol and Luna |
| Standard cached input | \$0.25 per 1M | \$0.50 per 1M | \$0.10 per 1M | Relevant for repeated prompts and persistent instructions |
| Standard cache writes | \$3.125 per 1M | \$6.25 per 1M | \$1.25 per 1M | Cache design affects recurring workload cost |
| Standard output price | \$15.00 per 1M | \$30.00 per 1M | \$6.00 per 1M | Output-heavy workloads require careful cost modeling |
| Context window | 1.05M tokens | 1.05M tokens | 1.05M tokens | All three support large-context applications |
| Maximum output | 128K tokens | 128K tokens | 128K tokens | Suitable for extensive responses when needed |
| General positioning | Intelligence-and-cost balance | Complex professional work | Cost-sensitive, high-volume work | No model is universally preferable |
| Likely scenario | Routine development, agents, and knowledge work | Highest-complexity reasoning and coding | Simple or high-volume production tasks | Evaluate against internal workloads |
OpenAI recommends Sol for complex reasoning and coding, Terra for balancing intelligence and cost, and Luna for cost-sensitive, high-volume workloads.
Terra may therefore suit teams that find Luna insufficient for a workload but cannot justify Sol’s higher token rates across every request.
How Do I Access GPT-5.6 Terra Through Gate.AI?
The Gate.AI model card lists GPT-5.6 Terra under the provider-qualified model ID:
openai/gpt-5.6-terra
Gate.AI provides an OpenAI-compatible interface with the base URL:
https://api.gate.ai/openai/v1
Gate.AI documentation specifies bearer-token authentication, the /chat/completions endpoint, streaming support, and model IDs in provider/model format.
Before production use, confirm that openai/gpt-5.6-terra remains visible to the relevant Gate.AI account and review the current model-card price.
Python Example
import osfrom openai import OpenAIapi_key = os.environ.get("GATEAI_API_KEY")if not api_key:raise RuntimeError("Set the GATEAI_API_KEY environment variable.")client = OpenAI(api_key=api_key,base_url="https://api.gate.ai/openai/v1",)response = client.chat.completions.create(model="openai/gpt-5.6-terra",messages=[{"role": "user","content": ("Review this deployment plan. Return the main risks, ""recommended mitigations, and unresolved questions."),}],)print(response.choices[0].message.content)
curl Example
curl https://api.gate.ai/openai/v1/chat/completions \-H "Authorization: Bearer $GATEAI_API_KEY" \-H "Content-Type: application/json" \-d '{"model": "openai/gpt-5.6-terra","messages": [{"role": "user","content": "Identify edge cases in this API migration plan."}]}'
Gate.AI documentation explicitly distinguishes its OpenAI-compatible base path, /openai/v1, from a generic /v1 path. The platform also documents model discovery through GET /models and recommends copying exact provider-qualified identifiers from the model marketplace.
FAQs
What is GPT-5.6 Terra’s context window?
GPT-5.6 Terra supports a 1,050,000-token context window and up to 128,000 output tokens as of July 2026. Requests containing more than 272,000 input tokens are billed at higher long-context input and output rates for the complete request.
How much does GPT-5.6 Terra cost?
OpenAI’s standard API price is \$2.50 per million input tokens, \$0.25 per million cached-input tokens, \$3.125 per million cache-write tokens, and \$15 per million output tokens as of July 2026. Long-context requests above 272K input tokens use higher rates.
How can developers access GPT-5.6 Terra?
Developers can access it directly through the OpenAI API using gpt-5.6-terra. The Gate.AI model card lists openai/gpt-5.6-terra, accessible through Gate.AI’s OpenAI-compatible base URL with bearer-token authentication, subject to current account availability.
What workloads may suit GPT-5.6 Terra?
Terra may fit software development, repository analysis, technical research, document processing, visual analysis, and tool-using agents. It is positioned between GPT-5.6 Sol’s flagship capability tier and GPT-5.6 Luna’s lower-cost, high-volume tier.


