Skip to main content

openai/gpt-5.6-terra/chat

GPT 5.6 Terra fits everyday coding and document tasks with a clear boundary. Define a concrete result, provide the local evidence needed to produce it and check the output against that contract before moving on.

Input $1.60Output $9.60per 1 million tokens20% below the publisher's list priceCached input $0.16Cache write $2Prompts over 272K tokensInput $3.20Cached input $0.32Cache write $4Output $14.40OpenAI official priceInput $2Output $12

Workbench

GPT 5.6 Terra

What can GPT 5.6 Terra help with?

Related models and next tasks

Missing the model you need?

GPT 5.6 Terra fits everyday coding and document tasks with a clear boundary. Define a concrete result, provide the local evidence needed to produce it and check the output against that contract before moving on.

Key numbers

Output limit (tokens)
128k

Token budget

Input window
922,000
tokens in one request
Longest reply
128,000
14% of the window

reasoning_effort

  • none
  • low
  • mediumdefault
  • high
  • xhigh
  • max
messages
up to 256
tools
up to 128

What it does

Shift handoff

Terra offers six levels of reasoning: none, low, medium, high, xhigh and max. The default medium setting can be adjusted for the problem at hand. A focused extraction may need little deliberation, whereas reconciling inconsistent records benefits from room to examine competing explanations before choosing a result. The model can take a screenshot, a short specification and the code that implements a feature as one conversation. Function calls let your program supply missing records or validate a proposed action during that discussion. Your program owns execution and authorization, and should return the matching call result so Terra can finish from observed facts rather than an assumed outcome.

What a call to GPT 5.6 Terra looks like

Request bodies from this family's own examples: roles, parameters and attachments exactly as they are sent. Each one is checked against the model's input schema before it is published.

  • Applied task

    user

    Extract the duty, owner and deadline from this note as JSON. Use unknown for missing details: The release manager will review retry logs tomorrow. Today is 2026-11-03. Answer in at most 75 words.

    max_tokens384reasoning_effortnone
  • Write a shift handoff

    user

    Turn this note into a concise shift handoff: The queue is empty. The export for customer 18 is waiting for approval. Priya owns the review due at 16:00 UTC. Answer in at most 75 words.

    max_tokens384reasoning_effortnone
  • Answer from a provided source

    user

    Using only this source, answer when the museum closes on Friday. Source: Tuesday to Thursday 09:00–17:00; Friday 09:00–20:00; closed Monday. Answer in at most 75 words.

    max_tokens384reasoning_effortnone

Where it fits

  • Use cases

    For a maintenance change, provide the existing behavior and a small before-and-after example. Ask Terra to modify the owning module and explain which caller assumptions might change. Confirm the proposed behavior with the checks associated with that module. For a weekly operations digest, submit labeled incidents and a fixed reporting window. Request a concise account of customer impact, resolved items and actions still open. Validate dates and incident identifiers before distributing the digest to its intended readers.

Model reference

GPT 5.6 Terra API reference

How to call the GPT 5.6 Terra API

  1. Prompt guide & Pro tips

    Keep the task boundary explicit: name the deliverable, the information that controls it and the conditions that make it acceptable. Include a counterexample when nearby categories are easy to confuse. If the source material has conflicting dates or values, ask Terra to retain the conflict and identify what would resolve it instead of selecting an unsupported answer. Use a JSON schema for a programmatic handoff and validate required fields after generation. Set an output allowance large enough for reasoning as well as the visible reply; the maximum is 128,000 tokens. Explicit sampling parameters apply only with reasoning none. For repeated jobs, keep stable instructions consistent, limit concurrency in your application and compare the cost per accepted result at the effort settings that meet your accuracy target.

GPT 5.6 Terra API questions

All GPT models18