Terra targets the high-volume middle of the model range
OpenAI has released GPT-6.1 Terra, positioning it between low-cost general models and the company’s more expensive frontier systems. The model combines image analysis, computer use and natural writing for work such as reading invoices, interpreting technical drawings, completing forms and editing media. It is available through ChatGPT Work, Codex and the API as gpt-6.1-terra.
Standard API pricing is US$1 per million input tokens, five cents per million cached input tokens and US$5 per million output tokens. The model supports a 1.05-million-token context window, up to 128,000 output tokens and reasoning efforts from none through max. Tool calling requires the Responses API even though text requests also work through Chat Completions.
Computer-use gains come with lower task cost
On Agents’ Last Exam, OpenAI says Terra at medium effort scores 15 percentage points above GPT-5.6 Terra at about one-third the cost. It reports performance near GPT-6 Astra at one-tenth the token price and completion times more than three times faster than Astra and GPT-6.1 Sol. These comparisons depend on the benchmark, tool environment and pricing assumptions.
The model also improves visual reasoning and coding. OpenAI reports a 50.3 per cent solve rate on Terminal-Bench 4.0 at maximum effort, compared with 21.5 per cent for the earlier Terra. On an internal set of prompts designed to induce errors, low-effort error rate fell from 53.6 to 16.7 per cent, while maximum effort reached 4.3 per cent.
Availability spans ChatGPT Work, Codex and the API
Lower cost can expand automation into high-volume workflows where mistakes accumulate quickly. Invoice entry, catalogue matching and application-screen actions need field-level checks, constrained destinations and clear rules for ambiguous evidence. Speed should not reduce the time allowed for approval when an action changes financial, customer or production records.
The launch gives teams another point on the capability-cost curve rather than one universally best model. Buyers should evaluate Terra against Luna, Sol, Astra and external alternatives using complete task cost, including retries and review. A cheaper token is valuable only when the workflow reaches an acceptable result with fewer interventions and predictable failure handling.
What teams should validate before production
For implementation, teams should record the exact model, software, dataset, connector and policy versions behind every result. Representative evaluation must include normal work, boundary cases, deliberate misuse and component failure, with outcomes separated by user role, data sensitivity and consequence. A strong average should never hide a serious failure in a critical path. Changes should pass the same regression set before promotion, and operators need a documented fallback that preserves evidence rather than silently broadening access or lowering quality.
Procurement and planning should account for the human work required to review exceptions, maintain controls and investigate incidents. Published performance or efficiency claims are useful starting points, but production confidence comes from evidence collected in the organisation’s own environment. A named owner, measurable acceptance threshold, cost model and tested shutdown path turn a promising release into a service that can be governed over time. Where decisions affect safety, rights, money or regulated records, accountable professional review remains essential.
Security and operational evidence
Security review should map every identity, credential, network destination, stored artefact and administrative access path involved in the workflow. Logs need enough context to reconstruct who initiated an action, which evidence was consulted, what the system proposed and what ultimately executed. Sensitive prompts and traces should not be retained merely because they are useful for debugging. Retention, redaction and access must follow the underlying data classification, with a practical process for correcting or removing material when policy or law requires it.
Operational monitoring should measure quality and service behaviour together. Latency, throughput and availability matter, but so do unsupported claims, missed constraints, unsafe tool calls and the rate at which people overturn recommendations. Teams should rehearse dependency outages and partial failures before unattended operation. If a model, connector or external service becomes unavailable, the workflow should fail predictably, preserve its state and tell the user what remains unfinished. Clear degradation is safer than an agent improvising around a missing control.
Transparency should scale with adoption
Organisations should explain the scope and limitations of the deployed capability to the people affected by it. Users need to know when automation is involved, how to challenge an outcome and where a human can intervene. That transparency improves feedback and prevents a pilot result from being interpreted as blanket approval for broader autonomy. Expansion should follow demonstrated evidence, not novelty or pressure to match a competitor announcement. The durable advantage comes from dependable integration, careful measurement and learning that survives the next model or product update.
Finally, teams should schedule a review after real usage rather than treating launch as the end of governance. The review should compare expected benefits with observed quality, cost, incidents and user behaviour, then retire workflows that do not justify their complexity. A service that works well can expand through the same evidence-based process. A service that fails should be narrowed or stopped without losing the records needed to understand why. This feedback loop is what turns experimentation into accountable operational capability.