What is GPT 5.6 Terra?
GPT-5.6 Terra is the middle tier of OpenAI’s GPT-5.6 family, and the official model page describes it in one sentence: it is designed for workloads that balance intelligence and cost, and it roughly corresponds to the mini model tier used in earlier GPT-5 families. The model catalog summarises it the same way, as the GPT-5.6 model that balances intelligence and cost; the family page calls it a lower-cost model with performance competitive with GPT-5.5; and the family guide’s own recommendation is to use it for strong performance at a lower price. The naming scheme is new with this generation: the number identifies the generation, while Sol, Terra and Luna are durable capability tiers that can advance on their own, and the three positions run flagship, balanced and fastest-and-cheapest in that order. OpenAI writes the name GPT-5.6 Terra, while this site’s own label for it — the one the heading and the navigation show — drops the hyphen and reads GPT 5.6 Terra; both appear here, and the model code settles which is meant. Its API model code is gpt-5.6-terra, its default snapshot is the same string with no dated suffix, the documented context window is 1,050,000 tokens, the documented maximum input is 922,000 tokens, the documented maximum output is 128,000 tokens, the documented inputs are text and image, the documented output is text, and the knowledge cutoff is 16 February 2026. Two statements about naming should be separated before anything else. The family alias gpt-5.6 does not point here: the official guide states that the gpt-5.6 alias routes requests to gpt-5.6-sol, and this model is not published with an alias of its own. And there is no gpt-5.6-mini: a request for that model ID returns a not-found page, because the slot that name suggests is the one this model took over. On currency, the model catalog now features GPT-6 Astra, GPT-6.1 Sol and GPT-6 Luna, and describes GPT-6 Astra as the flagship model for complex reasoning and coding, so this generation has been succeeded; the deprecations page, meanwhile, lists gpt-5.6-terra in neither its upcoming nor its past table, and instead prints it in the replacement column for fifteen older models. Succeeded and deprecated are different states, and both official pages are reported here rather than one of them being picked.
What GPT-5.6 Terra is worth using for
Half the flagship’s rate, until the long-context line reprices the whole request
The model page prints three figures and two rules, and the rules matter as much as the figures. Input is $2 per million tokens, cached input is $0.2 per million, and output is $12 per million. Cross 272,000 input tokens and the same prompt is priced at 2x input and 1.5x output for the full request, so the whole call is repriced rather than only the excess. Cache writes are billed at 1.25 times the uncached input rate, the generation-wide change that gives cache-write tokens their own column. The pricing page fills in the rest. At or under the threshold the four figures for gpt-5.6-terra are $2.00 input, $0.20 cached input, $2.50 cache writes and $12.00 output; above it they become $4.00, $0.40, $5.00 and $18.00. Batch and Flex are half the standard rate, so $1.00, $0.10, $1.25 and $6.00 short and $2.00, $0.20, $2.50 and $9.00 long. Fast is twice the standard rate, at $4.00, $0.40, $5.00 and $24.00 short and $8.00, $0.80, $10.00 and $36.00 long; it is the renamed form of what used to be called Priority, and the rename is dated 30 July 2026. Ultrafast carries a gpt-6-astra row and no row for this model. Regional processing for data residency adds 10% for models released on or after 5 March 2026, and FedRAMP endpoints add 10% as well. The clearest single proof that this is half the flagship sits on the model page’s own quick comparison table, which prints three rows — GPT-5.6 Terra at $2, $0.2 and $12, GPT-5.6 Sol at $4, $0.4 and $20, and GPT-5.4 Mini at $0.75, $0.075 and $4.5 — so the ratio and the tier this model replaces both come from one table.
One model is documented at $2 per million input tokens and $12 per million output tokens, with a long-context tier that doubles input and multiplies output by 1.5 for the whole request once a prompt crosses 272,000 tokens, and with cache writes charged at 1.25 times the uncached rate. Explain how a prompt that crosses the threshold is repriced, where cache writes show up on a bill, and how batch and fast processing change those same four line items.
Three separate official statements put this model in the mini slot
The claim that Terra inherits the mini tier is not a reading; it is written down three times in three different places. The model page says it in its own voice, writing that the tier roughly corresponds to the mini model tier used in earlier GPT-5 families. The model page’s quick comparison table says it in layout, by printing GPT-5.4 Mini as the third row beside Terra and Sol. The deprecations table says it in mapping, by handing gpt-5-mini-2025-08-07 to gpt-5.6-terra while gpt-5-2025-08-07 goes to gpt-5.6-sol and gpt-5-nano-2025-08-07 goes to gpt-5.6-luna — a one-to-one handover per tier. A fourth statement is indirect but explicit: the upgrade guide’s decision table tells callers to map a mini model, a balanced lower-cost route or a medium-throughput worker to gpt-5.6-terra, gives the reason as Terra is the mini-like tier, and adds that a flagship replacement can change latency and cost materially and that each role should be mapped to Sol, Terra or Luna rather than everything moving to Sol. What is absent is worth stating too: there is no gpt-5.6-mini. A request for that model ID returns a not-found page, because this model took the slot rather than sharing it.
Three official pages put one model in the slot a smaller previous-generation model used to occupy: one says so in prose, one prints that older model beside it in a price table, and one lists it as the replacement target in a deprecation map. Write me a short justification I can paste into an architecture decision record, citing the shape of each piece of evidence and noting what is not being claimed.
Fifteen retired models name this model as their replacement
The deprecations page is a two-column table — what is going away, and what to use instead — and gpt-5.6-terra appears fifteen times in the replacement column while appearing in neither of the tables that list retiring models. The dates split four ways: one entry is dated 11 December 2026, six are dated 23 October 2026, four are dated 23 July 2026 and four carry a 2026-09-28 date. The names being pointed here are the small end of several generations, among them gpt-5-mini-2025-08-07, o4-mini and o4-mini-2025-04-16, computer-use-preview and its dated snapshot, gpt-4o-mini-search-preview and gpt-4o-search-preview, gpt-5.1-codex-mini, gpt-3.5-turbo with several of its variants, and the legacy base models babbage-002 and davinci-002. Four of the fifteen carry an ft- prefix, which is the fine-tuning namespace, and the same model page marks fine-tuning as not supported for this model — both official statements are reported here rather than smoothed into one. The practical reading for anyone migrating is that this is not one upgrade path but a consolidation point: the workloads that used to sit on separate small models are all being pointed at the same target.
A deprecation table lists fifteen different retired models — including search previews, a computer-use preview, a codex mini variant and legacy base models — with the same model as the recommended replacement, spread across four different retirement dates. Draft a migration plan that sequences those workloads, flags which ones need re-testing rather than a string swap, and says what to check before switching.
The flagship carries a dated rate; this model carries a dated cut that already happened
This is where the two siblings differ most, and the difference is easy to get wrong. GPT-5.6 Sol’s model page attaches an end date to its rate, stating that the reduced figure is available at least through 21 November 2026. Terra’s model page states no such thing: it prints three rates and the two long-context rules and stops, and the one dated sentence on the pricing page names GPT-5.6 Sol alone. The only dated price fact attached to this model is a completed event, written as history in the family page’s availability section, which carries an update dated 30 July 2026 recording that OpenAI cut the price of GPT-5.6 Terra by 20%. The same section still prints the launch figures next to it, $2.50 per million input tokens and $15 per million output tokens, and the arithmetic closes: $2.50 × 0.8 = $2.00 and $15 × 0.8 = $12.00, which is exactly what the model page, the pricing page and the quick comparison table all print today. So a launch price and a dated reduction sit side by side on one official page, and neither of them is a live offer with an end date. This page therefore quotes the current rates with no expiry attached, because the official sources do not give one, and a summary that carries the flagship’s November date over to this model has moved it without cause.
Two models from the same family: one page attaches an end date to a reduced rate, the other states only current rates plus a past-dated price reduction. Show me how to write the price section for the second model without importing the first model’s deadline, and how to present the launch price beside the current one so the arithmetic is checkable.
Official GPT-5.6 Terra specifications
- Developer
- OpenAI
- Model ID
- gpt-5.6-terra
- Official context window
- 1,050,000 tokens
- Official maximum output
- 128,000 tokens
- Official inputs
- Text and image
- Output
- Text
GPT-5.6 Terra and GPT-5.6 Sol side by side
Every value below comes from a single page — the GPT-5.6 family announcement on openai.com, checked on 30 September 2026 — and from a single table family within it. That page carries eleven HTML tables, one per evaluation group, and both the GPT-5.6 Terra and the GPT-5.6 Sol column are present in all eleven. Thirty-nine rows report a value for both models, and all thirty-nine are reproduced here, in the order the official page prints them, so nothing is dropped for going the wrong way and nothing is selected for going the right way. The left column is this page’s model, the middle column is GPT-5.6 Sol, the tier above it; a third GPT-5.5 column exists on the same page and is not reproduced here. Read the direction first, because it is not the direction a reader assumes: Terra wins two of the thirty-nine rows and loses thirty-seven. The two wins are worth naming, since both sit in the self-improvement group and both are wide — NanoGPT at 14.5 against 9.69 and PostTrainBench Lite at 51.5 against 50.3. Among the thirty-seven losses the margins run from a near-tie such as Internal Research Debugging Evaluation at 67.8 against 68.3 up to FrontierMath Tier 4 at 68.3 against 83, ExploitBench at 52.9 against 73.5 and OSWorld 2.0 at 50.2 against 62.6. One row deserves reading twice for a different reason: on the long-context recall test MRCR v2 eight-needle at 512K–1M, Terra scores 72.5, Sol scores 73.8 and GPT-5.5 scores 74, which makes this the one row in the set where the lower tier is below both — and it sits in the same group as the row with the widest gap, GraphWalks BFS 256k f1 at 76.9 against 90.7. Two groups are labelled internal by OpenAI itself, and those rows are the provider’s own evaluations rather than public benchmarks: Management Consulting Tasks and MedChemBench. One conflict inside that same official page is recorded rather than smoothed over: its prose says the generation sets a new high of 53.6 on Agents’ Last Exam, while its own tables print 52.7% for Sol and 50.4% for Terra. This page uses the table values and reports the discrepancy. One further figure travels with the ExploitGym row, where the table prints the six-hour result at 33.7% for Sol and the prose adds that the two-hour figure rose from 15.1% to 24.9%. These are provider evaluations of the models, not measurements of this website, and no score here predicts the quality or speed of your conversation.
| Official evaluation | GPT 5.6 Terra | GPT-5.6 Sol |
|---|---|---|
| Professional · Agents’ Last Exam | 50.4% | 52.7% |
| Professional · GDPval-AA v2 | 1,593 Elo | 1,747.8 Elo |
| Professional · Management Consulting Tasks (Internal) | 37.2% | 43.2% |
| Professional · Big Finance Bench | 51% | 53% |
| Professional · Artificial Analysis Intelligence Index v4.1 | 55 | 58.9 |
| Coding · Artificial Analysis Coding Agent Index v1.1 | 77.4 | 80 |
| Coding · SWE-Bench Pro | 63.4% | 64.6% |
| Coding · DeepSWE v1.1 | 69.6% | 72.7% |
| Coding · Terminal-Bench 2.1 | 87.4% | 88.8% |
| Science and health · GeneBench Pro | 23.3% | 28.7% |
| Science and health · LifeSciBench | 56% | 59.9% |
| Science and health · MedChemBench (Internal) | 35% | 48.3% |
| Science and health · HealthBench Professional | 57.7% | 60.5% |
| Computer use · OSWorld 2.0 | 50.2% | 62.6% |
| Computer use · BrowseComp | 87.5% | 90.4% |
| Computer use · BenchCAD | 62.3% | 70.6% |
| Computer use · BenchCAD (python tool) | 78.2% | 83.4% |
| Cybersecurity · Capture-the-Flag Challenges | 91.8% | 96.7% |
| Cybersecurity · SEC-Bench Pro | 57.7% | 71.2% |
| Cybersecurity · ExploitBench | 52.9% | 73.5% |
| Cybersecurity · ExploitGym | 23.2% | 33.7% |
| Self-improvement · Internal Research Debugging Evaluation | 67.8% | 68.3% |
| Self-improvement · KernelGen 1P | 49.2% | 61.1% |
| Self-improvement · NanoGPT | 14.5% | 9.69% |
| Self-improvement · PostTrainBench Lite | 51.5% | 50.3% |
| Self-improvement · RSI Index | 56.3% | 57.9% |
| Multimodal · MMMU Pro (no tools) | 80.7% | 83% |
| Multimodal · MMMU Pro (with tools) | 82% | 84.6% |
| Multimodal · gdp.pdf | 24.7% | 30.7% |
| Academic · GPQA Diamond | 92.9% | 94.6% |
| Academic · FrontierMath Tier 1-3 (v2) | 84.9% | 89% |
| Academic · FrontierMath Tier 4 (v2) | 68.3% | 83% |
| Tool use · AutomationBench | 15.2% | 18.1% |
| Tool use · Toolathlon | 53.1% | 58% |
| Long context · OpenAI MRCR v2 8-needle 256K-512K | 89.6% | 91.5% |
| Long context · OpenAI MRCR v2 8-needle 512K-1M | 72.5% | 73.8% |
| Long context · GraphWalks BFS 256k f1 | 76.9% | 90.7% |
| Long context · GraphWalks BFS 1mil f1 | 71.2% | 77.1% |
| Abstract reasoning · ARC-AGI-3 | 0.8% | 7.78% |
How to use GPT 5.6 Terra online
Choose the model
This page opens with GPT 5.6 Terra selected. The model navigation on the left and the selector inside the chat box stay in sync, and switching models keeps the current conversation, so start a new chat when you want a clean context. Three naming facts are worth fixing before you send anything. Two spellings of the name appear on this page and both are correct in their own place: the official model code is gpt-5.6-terra, and the site’s own display label, which is what the navigation and the heading show, omits the hyphen. The family alias gpt-5.6 does not point here — it routes to gpt-5.6-sol — and this model is not published with an alias of its own. And there is no gpt-5.6-mini model ID; the slot that name suggests is the one this model took over.
Decide what you expect from reasoning, because this box will not ask
The family documentation lists six reasoning efforts — none, low, medium, high, xhigh and max — with medium as the default when the setting is omitted, plus a separate pro execution mode available in the Responses API whose supported efforts begin at medium. Persisted reasoning is the part that affects a long session: for this generation the default is to carry earlier turns forward, and reasoning can be reused only within the same model family, so gpt-5.6-sol, gpt-5.6-terra and gpt-5.6-luna can reuse each other’s reasoning while nothing carries between this family and GPT-5.5. Reasoning tokens are never shown to the caller, still occupy space in the context window, and are billed as output tokens, so their cost lands in whatever follows them. None of that is selectable here: the catalog entry marks reasoning as unsupported, so the provider default is what runs. The family guidance also notes that this generation tends to be more concise than GPT-5.5 by default and exposes answer length as a separate parameter, which this box does not surface either — so state the length you want in the prompt itself.
Sign in, send, and check the cost against the official pages
Sending a message needs an account with available points. The composer reads a reference price from the live model catalog and a finished request reports what it actually cost. Two ceilings are set by this site rather than by the model, so plan around them: replies are requested with at most 4,096 output tokens, and there is no way to raise or inspect the reasoning effort from here. Because the rates quoted on this page are the current standard rates printed by the official pages, re-check them there before relying on a figure for planning, and treat any third-party summary that still quotes a launch price as out of date.
What GPT 5.6 Terra costs, and why this page carries no end date
This model has no end date on it, and that absence is the first thing to establish. The official model page prints three rates for gpt-5.6-terra and two long-context rules and stops there, and the one dated sentence on the pricing page names GPT-5.6 Sol. So the figures below are current standard rates with no window attached, and the only dated price event in this model’s record is a completed one. Both pages were checked on 1 October 2026. At or under 272,000 input tokens the rate is $2.00 per million input tokens, $0.20 per million cached input tokens, $2.50 per million cache-write tokens and $12.00 per million output tokens; above that threshold the same four figures become $4.00, $0.40, $5.00 and $18.00. The stated rule is that prompts with more than 272K input tokens are priced at 2x input and 1.5x output for the full request, so crossing the line reprices the entire request rather than only the excess. Cache writes are billed at 1.25 times the uncached input rate, which is why cache-write tokens get their own column. Batch and Flex are half the standard rate and Fast is twice it, with Fast being the renamed form of what used to be called Priority and the rename dated 30 July 2026; Ultrafast has a row for gpt-6-astra and none for this model. Regional processing for data residency adds 10% for models released on or after 5 March 2026, and FedRAMP endpoints add 10% as well. The dated part is history, not an offer. The family page’s availability section still prints the launch figures for this model — $2.50 per million input tokens and $15 per million output tokens — and carries an update dated 30 July 2026 recording that OpenAI cut the price of GPT-5.6 Terra by 20%. The arithmetic closes on both figures: $2.50 × 0.8 = $2.00 and $15 × 0.8 = $12.00, which is exactly what the model page, the pricing page and the model page’s quick comparison table all print today. So the launch price and the reduction sit side by side on one official page, and neither is a live offer with an end date. A summary that carries the flagship’s November date over to this model has moved it without cause. This site charges none of those figures. It bills points, and the catalog reference price behind this page is 153 points per million input tokens, 918 per million output tokens and 15.3 per million cached input tokens, with no conversion between those and the official dollar rates.
View points and plans ↗GPT 5.6 Terra FAQ
What does GPT 5.6 Terra cost, and will the price change?
The current standard rates printed by the official pages are $2.00 per million input tokens, $0.20 per million cached input tokens and $12.00 per million output tokens, with a long-context tier above 272,000 input tokens at $4.00, $0.40 and $18.00 plus $5.00 for cache writes. Batch and Flex take half the standard rate, Fast takes twice, and data residency and FedRAMP endpoints each add 10%. On whether it will change: this page attaches no end date, because the official sources give none — the model page prints rates and long-context rules only, and the one dated sentence on the pricing page names GPT-5.6 Sol. The single dated price fact about this model is a completed one, an update dated 30 July 2026 recording that OpenAI cut its price by 20%, printed beside the launch figures of $2.50 and $15 on the same page, and the arithmetic closes at $2.50 × 0.8 = $2.00 and $15 × 0.8 = $12.00. None of this is this site’s checkout price: this workspace bills points, at 153 points per million input tokens and 918 per million output tokens.
How does GPT 5.6 Terra compare with GPT-5.6 Sol in OpenAI’s own tables?
Across the thirty-nine rows that report both models, Terra wins two and loses thirty-seven. Both wins are in the self-improvement group: NanoGPT at 14.5 against 9.69 and PostTrainBench Lite at 51.5 against 50.3. The margins among the thirty-seven losses run from Internal Research Debugging Evaluation at 67.8 against 68.3 out to FrontierMath Tier 4 at 68.3 against 83, ExploitBench at 52.9 against 73.5 and OSWorld 2.0 at 50.2 against 62.6. One row needs stating plainly: on MRCR v2 eight-needle at 512K–1M, this model reads 72.5, Sol reads 73.8 and the GPT-5.5 column on the same page reads 74, so the lower tier is below both. All of these are provider evaluations of the models, not measurements of this website.
Is GPT 5.6 Terra the successor to the older mini models?
Three separate official statements say yes, and they are independent of each other. The model page’s own prose says the tier roughly corresponds to the mini model tier used in earlier GPT-5 families. The model page’s quick comparison table says it in layout, printing GPT-5.4 Mini as the third row beside Terra and Sol. The deprecations table says it in mapping, sending gpt-5-mini-2025-08-07 to gpt-5.6-terra while gpt-5-2025-08-07 goes to Sol and gpt-5-nano-2025-08-07 goes to Luna. A fourth statement is indirect but explicit: the upgrade guide’s decision table maps a mini model, a balanced lower-cost route or a medium-throughput worker to gpt-5.6-terra and gives the reason as Terra is the mini-like tier. One absence is also worth noting: there is no gpt-5.6-mini model ID.
What are the context window and the maximum output?
The model page documents a 1,050,000-token context window, a maximum input of 922,000 tokens, a maximum output of 128,000 tokens, text and image as inputs, text as output, a knowledge cutoff of 16 February 2026, and a snapshot list whose only entry is gpt-5.6-terra. Two of those three numbers are easy to confuse. The maximum input is smaller than the whole context window, which is usual, but the figure is printed on the model page rather than inferred. And this page is not running against that output ceiling: replies here are requested with at most 4,096 output tokens, the smaller of the catalog’s declared 16,384 and the composer’s hard ceiling, so plan long answers as a sequence rather than one long reply.
Which reasoning levels exist, and which one runs here?
Six exist and none of them is selectable on this page. The model page lists none, low, medium, high, xhigh and max, with medium as the default when the setting is omitted. On top of the levels there is a separate execution mode, pro, available in the Responses API and working with any GPT-5.6 model, whose supported efforts begin at medium and whose aggregated tokens are billed at the model’s standard rates. Persisted reasoning defaults to carrying earlier turns forward for this generation and can be reused only within the same model family, so gpt-5.6-sol, gpt-5.6-terra and gpt-5.6-luna can reuse each other’s reasoning while nothing carries between this family and GPT-5.5. Reasoning tokens are never shown to the caller but still occupy the context window and are still billed as output tokens. This chat box has no level selector and no off switch, because the catalog entry behind the page marks reasoning as unsupported, so the provider default applies.
Do images and PDFs work, and does the detail level change the cost?
Images work. Attachments here accept JPEG, PNG and WebP files and PDFs at up to 24 MB each. There is no detail-level control on this page, so the provider default applies, and the documented behaviour is that with the detail level omitted or auto, image dimensions are preserved except that an image larger than 65,535 pixels on either side is scaled down, while anything exceeding the 30,000-patch limit is rejected rather than resized. One mechanism difference matters: a PDF here is converted to extracted text before it is sent rather than uploaded as a page image, so a scanned document or a complex layout may lose content and is better attached as an image or pasted as text.
What does this page expose compared with the official API?
Less than the official pages document, and the difference is listed rather than glossed over. Available here: text chat, streaming replies, image and PDF attachments up to 24 MB each, and a web-search toggle billed per search. Not available here: any context-window figure in the interface, because the catalog entry publishes none; any reasoning-effort selector, off switch or pro mode; the ten tools the official Responses API supports, including web search, file search, image generation, code interpreter, hosted shell, apply patch, skills, computer use, MCP and tool search; any image detail control; any verbosity control; any endpoint selector; and the five rate-limit tiers the model page lists. Two ceilings are set by this site rather than by the model: replies are requested with at most 4,096 output tokens, and the catalog entry declares 16,384, so the smaller number governs. Pricing is in points and is not a conversion of the official dollar rates.
Is NanoBanana Pro the official OpenAI website?
No. NanoBanana Pro is an independent platform providing a shared workspace for multiple AI models, and this page is a guide to one of them rather than a product page from its developer. OpenAI develops and publishes GPT-5.6 Terra; the official model page, the family announcement, the pricing page, the family usage guide, the upgrade guide, the reasoning guide, the model catalog and the deprecation list are all linked at the bottom of this page, and every specification, price and evaluation figure quoted here comes from one of them. If you need the developer’s own contract, rate limits or support, follow those links rather than relying on this page.
Sources and model information
Information checked
- OpenAI API documentation · GPT-5.6 Terra ↗
- OpenAI · GPT-5.6: frontier intelligence that scales with your ambition ↗
- OpenAI API documentation · Pricing ↗
- OpenAI API documentation · Using GPT-5.6 ↗
- OpenAI API documentation · Upgrading to GPT-5.6 Sol ↗
- OpenAI API documentation · Reasoning models ↗
- OpenAI API documentation · Model catalog ↗
- OpenAI API documentation · Deprecations ↗
Start a GPT 5.6 Terra conversation
The chat box above runs this model, and the guide on this page is written to be checked rather than trusted: the specifications come from the official model page, the comparison comes from the single official page whose eleven tables print both columns, and the places where official pages disagree with each other or with this workspace are named rather than smoothed over. Send the task the way you would brief a person — outcome, constraints, evidence, stopping condition — and re-check the figures against the pages linked below, since the only dated price event attached to this model is a completed one and the current rates carry no end date at all.
Start a chat with GPT 5.6 Terra ↑