The builder’s guide to GPT‑5.6

GPT‑5.6 sets a new standard for price-performance

The GPT‑5.6 model family makes frontier-level agent performance dramatically more affordable, while also advancing the frontier of what is possible.

In this guide, we show how startups are using smarter model selection and new API controls that help with reasoning continuity, multi-agent orchestration, and programmatic tool calling to build faster, more capable agents at a fraction of the cost.

A better out-of-the-box experience

Since GPT‑5, each model generation has sought to tackle longer-horizon tasks with fewer tokens. GPT‑5.6 continues that trajectory: stronger agent performance, lower costs, with minimal changes to the underlying harness.

The improvements in top-line cost efficiency are compounded with increased accuracy at lower reasoning efforts. For example, on Agents’ Last Exam, GPT‑5.6 Sol at “low” reasoning outperformed GPT‑5.5 at “high” reasoning when the harness was kept constant. We’ve seen similar success stories in production testing where startups report seeing significant cost improvements across a range of workflows by reducing the reasoning effort from the prior defaults.

Model Selection

Historically, upgrading to a flagship model at the highest reasoning available has been the best option for long-horizon use cases. This has been in large part due to these models being significantly more capable than cost-optimized models at handling longer contexts and tool calling. This has changed with the 5.6-family: with more test-time compute, Luna and Terra can often perform similar to GPT‑5.4 and 5.5 while being significantly cheaper.

1 of 3

Consider tasks in BrowseComp: a search-based benchmark that tests a model’s ability to search for obscure facts. Three months ago, GPT‑5.5 (Extra High) scored 84.36% on this benchmark for a total cost of $33.27. At launch, GPT‑5.6 Luna (Extra High) delivers essentially the same performance, scoring 84.04% at a cost of $1.33. We’ve since reduced prices further. Read more on our latest price cuts.

The smaller 5.6-family models are a strong fit for high-volume workloads, latency-sensitive interactions, and repeated steps within agentic workflows. For example, if you’re operating a legal-tech startup that parses handwritten memos prior to agentic analysis, instead of using a frontier model for the entire use case, you can now use Terra or Luna for extraction and register significant cost savings.

Evolving the Responses API to architect more efficient agents

In addition to making GPT‑5.6 more performant out of the box, we also shipped new primitives to the Responses API to unlock further gains. We trained GPT‑5.6 end-to-end with three complementary architectural interventions that enable agents to operate more efficiently:

1. Reuse work already performed: by allowing reasoning to be persisted⁠(opens in a new window) across model turns and using native compaction⁠(opens in a new window) to compress long-running conversations, the model can maintain coherence in its work across longer task horizons without getting confused or having to reconstruct prior context.

2. Parallel decomposition where appropriate: using native multi-agent orchestration⁠(opens in a new window) allows coordinating multiple agents across parallel workstreams to finish complex tasks faster.

3. Move deterministic work into code: using programmatic tool calling⁠(opens in a new window) to filter, aggregate, and orchestrate tool outputs outside the model’s context window, reserving model tokens for judgment and reducing cost, latency, and context rot.

Used together, the difference can be dramatic. For example, on ARC-AGI-3, GPT‑5.6 Sol scored 13.3% with the standard harness. After enabling retained reasoning and compaction, however, the score jumped to 38.3%—while using roughly 6× fewer output tokens. No changes to the model, but nearly three times the performance. You can read more on our ARC-AGI-3 harness investigation here.

Programmatic Tool Calling

Agentic workflows often involve two kinds of work:

1. Tasks that require judgment

2. Work that mostly requires moving, filtering, and combining data

When an agent retrieves 100 filings, filters them by date, and identifies relevant transactions, the model shouldn’t have to reason over every intermediate result in its context window. Programmatic Tool Calling lets GPT‑5.6 write JavaScript to orchestrate tools, run independent calls in parallel, and process their outputs outside the context window. The model is left to focus on what requires intelligence: applying judgment.

Multi-agent

On complex, parallelizable tasks, distributing actions and reasoning across multiple agent workstreams enables faster task completion as well as higher intelligence. In these setups, the primary agent is responsible for orchestrating the subagents and delegating tasks to them. The subagents pursue their objectives in parallel and finally pass back their output to the primary agent for final synthesis. Teams can start leveraging multi-agent natively by enabling multi-agent⁠(opens in a new window) in the Responses API. This is also how the ultra capability setting in ChatGPT works.

Although GPT‑5.6 has a strong sense of the appropriate number of subagents and when to spawn them, multi-agent behavior is very steerable. Instructing the model on when to invoke subagents can increase the likelihood of spawning agents only in situations where the additional token expenditures would result in better performance.

Prompt Caching

Across the entire family of models, the prompt cache TTL has been extended to a minimum of 30 minutes and cache breakpoints can now be set deterministically within a model’s context window. This has enabled startups to significantly improve their cache hit rate.

In addition to setting cache breakpoints, continuing to use an appropriate prompt_cache_key⁠(opens in a new window) increases the likelihood of requests landing on the same inference engine as one that previously served the same prefix, thereby reducing latency.

Conclusion

What stands out across these examples is how much the economics of building agents have changed.

Use cases that once required a frontier model at every step can now achieve comparable or better results at a fraction of the cost by using smaller models, tuning reasoning effort, and making efficient architectural choices.

We're excited to see what you all build!