A generated title card reading 'GPT-6.2 Sol Pro vs GPT-6.1 Sol Pro: same rate card, 40% fewer tokens', showing output tokens per index task falling from 67,824 to 40,360 and two pills giving the Intelligence Index moving from 54.6 to 57.3 and cost per task falling from $1.27 to $1.01, above a line stating the $2.00 input and $10.00 output rate is identical on both tiers.
Guides & Insights

GPT-6.2 Sol Pro vs GPT-6.1 Sol Pro: Same Rate Card, 40% Fewer Tokens

Author

jinhao.song

Date Published

Latest models · 20View all models →
Benchmarks: Artificial Analysis · updated daily
Back to all posts

Upgrading from GPT-6.1 Sol Pro to GPT-6.2 Sol Pro costs nothing on the price list. Both tiers bill $2.00 per million input tokens and $10.00 per million output, both carry a 1,050,000-token context window with 128,000 maximum output, and both call pro mode as reasoning.mode: pro on the base model rather than as a distinct identifier. The upgrade is worth making anyway, and the reason is the one figure that appears nowhere on OpenAI's rate card: at max effort, GPT-6.2 Sol spends 40,360 output tokens per Artificial Analysis index task where GPT-6.1 Sol spends 67,824. Forty percent less work, same meter, 20% off the bill at the end of it. Reviewed on 18 November 2026, one day after the 6.2 generation shipped.

Two things make this a subtler decision than the sticker suggests. The first is that the two models are not separated by a hardware generation or an architecture change you can point at — the context window is the same, the modality list is the same, the price is the same, and the only structural difference in OpenAI's documentation is a knowledge cutoff that moved from 30 April 2026 to 1 June 2026. The second is that the improvement is uneven: on the evaluations that matter for coding agents it is large, and on calibration it is negative. A comparison that only reports the composite index would miss both.

What actually differs, in the vendor's own specification

Side by side, from the two model pages on developers.openai.com, read on 18 November 2026:

• Price — $2.00 input / $0.10 cached / $2.50 cache write / $10.00 output per million tokens on both. Above 272,000 input tokens both go to $4.00 / $0.20 / $5.00 / $15.00.

• Context — 1,050,000 tokens, 922,000 max input, 128,000 max output, on both.

• Knowledge cutoff — 1 June 2026 vs 30 April 2026.

• Effort levels — low, medium, high, xhigh, max on both; both reject reasoning.effort: none.

• Reasoning modes — standard and pro in the Responses API on both, billing at standard token rates and differing only in how much work is aggregated.

• Ultrafast multiplier — 3× standard through 28 February 2027, then 6× on both.

• New on 6.2 — discounted background completion windows in the Responses API public beta: 30% below standard for a two-hour deferral, 40% below for eight hours.

• Behaviour change — from GPT-6.2 onward the API drops reasoning items when it detects a mid-conversation prefix edit, a model downgrade, an end-user change or an organisation change. Losing reasoning items can degrade answer quality and make the model repeat earlier work in fresh tokens.

That last line is the one to read twice, because it is a cost trap disguised as a correctness note. If your application edits instructions mid-conversation — which many agent loops do when they re-render a system prompt — the 6.2 generation will discard the reasoning it had accumulated, pay for it again on the next turn, and break the prompt cache that would otherwise have made the repeat cheap. On a pro-mode workload, where reasoning tokens are the majority of output, that is the difference between the 40% saving and no saving at all. OpenAI's own guidance is to keep the prefix unchanged when you change settings between responses.

Screenshot of OpenAI's documentation page for GPT-6.2 Sol, showing the model ID gpt-6.2-sol, a 1,050,000-token context window with 922,000 maximum input and 128,000 maximum output, a 1 June 2026 knowledge cutoff, and text-token pricing of $2 input, $0.10 cached input, $2.50 cache write and $10 output per million.

The independent numbers: 2.7 points and 20% per task

Artificial Analysis had both tiers measured at max effort on the same harness, which is the only way this comparison holds. Intelligence Index v5.0.1: 57.3 for GPT-6.2 Sol against 54.6 for GPT-6.1 Sol. Cost per index task: $1.01 against $1.27. On the current v5.0.1 board GPT-6.2 Sol sits 5th of 58 scored entries; GPT-6.1 Sol no longer appears on the leaderboard’s live list, so the comparison rests on the per-model measurements rather than on rank.

Neither of those is a dramatic number on its own. What makes the pair worth acting on is that they moved together — the newer model is both better and cheaper per unit of completed work while the price list sat perfectly still. That is the signature of an efficiency release rather than a repositioning, and it is the pattern you want to see before you migrate a production path.

Now the breakdown, which is where the two models diverge by more than the composite suggests:

• Terminal-Bench 4.0 — 60.1% vs 56.1%.

• Terminal-Bench Science — 67.6% vs 58.1%, a 9.5-point jump.

• HLE Diamond — 64.0% vs 58.8%.

• FrontierCode 2.0 — 44.4% vs 40.6%.

• AutomationBench — 71.3% vs 64.9%.

• AnalystAgent — 53.8% vs 50.0%.

• AA-Omniscience — 40.4 at 55.4% hallucination vs 42.0 at 51.9% hallucination.

Every capability row improves. The calibration row does not: the newer model is 3.5 points more likely to assert something it cannot support. That trade is close to free inside a coding agent that runs a test before declaring success, and it is a real regression inside a research workflow with no verification step. If your pro-mode usage is the second kind, this is not an automatic upgrade.

A generated two-column comparison scoreboard titled 'GPT-6.2 Sol vs GPT-6.1 Sol', with the left column GPT-6.2 Sol at 57.3 on the Intelligence Index, $1.01 cost per task, 40,360 output tokens per task, 60.1 percent on Terminal-Bench 4.0, 40.4 on AA-Omniscience and $2 input and $10 output per million, and the right column GPT-6.1 Sol at 54.6, $1.27, 67,824 tokens, 56.1 percent, 42.0 and the same $2 and $10 price, with a footer attributing the measurements to Artificial Analysis and the pricing to OpenAI.

Where the 40% comes from, line by line

Pro mode multiplies an unknown quantity of model work on top of a baseline token count, so the baseline is the only part you can reason about — and the independent data sizes it precisely.

At max effort, GPT-6.2 Sol averages 40,360 output tokens per index task: 22,800 reasoning and 17,561 answer. GPT-6.1 Sol averages 67,824: 49,213 reasoning and 18,611 answer. The visible answer barely moved — 6% shorter. The reasoning collapsed by 54%. That is the entire mechanism. The newer model thinks for less than half as long to produce an answer of the same length, and because reasoning tokens bill as output, that is where the saving lives.

Put dollars on it and the arithmetic is unglamorous: 40,360 tokens at $10/million is about $0.40 of output, against $0.72 for the older model. Input does not cooperate, though. Across the whole suite GPT-6.2 Sol bills about $0.61 of input per task against $0.55 for GPT-6.1 Sol — it reads more, not less, because its cache write and cache read volumes both rose. The output saving and the input penalty nearly cancel into the net $1.01-versus-$1.27 figure. Nothing in that transfer comes from a price cut, because there was no price cut.

The practical warning is the one implied by pro mode: because the multiplier is unknown and applies to whatever the model decides to do, a 40% smaller baseline does not guarantee a 40% smaller pro-mode bill. It guarantees a cheaper floor. Measure your own calls before you rewrite a budget.

Migrating without a code change

The mechanical migration is one string. Both models accept the same parameters, the same effort values, the same Responses API surface, and the same tool set, so the swap is model: "gpt-6.1-sol" to model: "gpt-6.2-sol" with pro mode configured identically. OpenAI's migration guide adds one required check for tool calling: it requires the Responses API, not Chat Completions, and that was already true on 6.1.

What is not one string is the reasoning-item behaviour described above. Before you flip the model, audit whether anything in your loop mutates the conversation prefix — dynamic system prompts, injected tool definitions that reorder, per-turn context trimming at the front. If it does, fix that first or the efficiency gain evaporates on the second turn.

Rollout posture matters too, because this is a one-day-old tier with one independent measurement behind it. The conservative path is to hold production on the 6.1 tier and evaluate 6.2 on the traffic you can check — a shadow route, a canary percentage, a test suite run against both. On OrcaRouter, openai/gpt-6.1-sol is on the catalogue at provider list price with 0% markup and automatic failover across providers, so the model already carrying your traffic can absorb a bad afternoon without you discovering it in production. GPT-6.2 Sol has not appeared on our catalogue as of 18 November, which is exactly the reason to run the evaluation as a comparison rather than a cutover.

The 6.1 tier also stays callable for a while: OpenAI's deprecations table still routes retiring GPT-5 and o3 workloads to gpt-6.1-sol as their replacement, with those shutdowns dated 11 December 2026. A model that is itself the recommended migration target for other models is not being retired imminently, so a deliberate, measured move to 6.2 costs you nothing in urgency.

Screenshot of the OrcaRouter model page for GPT-6.1 Sol, showing the model ID openai/gpt-6.1-sol, a 1,050,000-token context window with 128,000 maximum output, and pricing of $2.00 input and $10.00 output per million tokens at provider list price.

Who should move, and who should wait

Move now if your workload is terminal-heavy, tool-using or verification-gated. The 9.5-point Terminal-Bench Science jump and the 6.4-point AutomationBench jump are large enough that a canary run will show them, and the 20% per-task saving arrives without a negotiation or a new contract.

Wait if your workload is pro-mode research synthesis where the output is read rather than tested. The calibration regression is small but it points the wrong way, and the efficiency argument does not cover an error you only discover after publication. Wait, also, if your agent loop rewrites conversation prefixes — fix that first, then upgrade, then measure; upgrading before fixing will make the model look worse than it is.

Either way, the version number is doing less work here than it looks like it is. This is not a generation that bought capability with money. It is a generation that bought capability with tokens, and the bill moved in your favour for once.

Compared in this article1

Detected from this article · Benchmarks: Artificial Analysis · updated daily