What is guaranteed, and what is not
OpenAI guarantees the GPT-5.6 Sol promotional rate at least through 21 November 2026, and INFRO's updates timeline advises that budgets running past that date should use the standard rate 1. OpenAI's wording is "available at least through November 21, 2026": a floor, not an end date, and no later rate is dated 2.
Three things this article could not confirm, because OpenAI's own pricing page was not readable on 2 November:
- The post-promotion rate. None is published in the sources read.
- Which rate is the promotional one. INFRO's catalog lists GPT-5.6 Sol at $4.00 input, $20 output and $0.40 cached input per million tokens, checked 5 October 3. Whether that is the promotion or the standard rate is not stated there.
- What the promotion covers. Cached input, Batch, Flex, Fast mode and long context may or may not follow the same step. Read OpenAI's page before you sign anything.
So a defensible forecast has two columns: the listed rate until 21 November, and a range after it.
Before and after on three workloads
Workloads A and C are about 70% and 67% output cost, so a step that falls mainly on output would hit them harder than these uniform figures show. In November itself, a step on 22 November puts 9 of 30 days at the new rate: workload A at 2x lands near $11,180 instead of $8,600.
Workload B has a second lever. OpenAI lists Batch and Flex at half the standard rate 4; if Batch is offered for GPT-5.6 Sol on your account, B at today's rate halves to $3,600, which is below its 2x figure of $14,400 by a wide margin. Confirm the model is listed for Batch first.
Decision list: commit, switch tier or cap
Make the call per workload, not per account.
- Commit only where the workload is stable, you have already passed it on GPT-5.6 Sol, and the contract fixes a dollar rate for the term. Do not size a commitment on the promotional run-rate. INFRO's commitment forecast is the amount consumed plus the trailing 28-day daily mean times the days remaining, and it states that it does not model price changes 5. Enter the step yourself and compare.
- Switch tier where GPT-6 Sol could pass your own eval. At list it is half the GPT-5.6 Sol input and output rate in the table, and OpenAI lists GPT-6.1 Sol with the same rates and a lower cached-input rate 4. The saving only counts if the pass rate holds, so measure cost per successful task and re-run on the new snapshot; the method is in GPT-6 Astra, Sol or Luna.
- Cap everything that stays, before 21 November. A blocking budget admits a request only if its worst-case estimated cost fits the room left, and without
max_tokensthe worst case assumes the model's maximum output 6. Setmax_tokenson workload C in particular, since its output is reasoning-heavy.
Steps to take this week
- Pull November-to-date cost per project for GPT-5.6 Sol, split into fresh input, cached input and output.
- Read OpenAI's current pricing page and record the rate, the date and what the promotion covers.
- Put a 22 November row in your price schedule, as in the introductory-pricing guide, and forecast December at two or three step sizes.
- Ask your account contact whether your rate is fixed in dollars or relative to list.
- Start the GPT-6 Sol eval on the highest-spend workload first.
- Set blocking budgets and
max_tokenson the rest.
If requests go through INFRO, per-request estimated cost by project and key shows which workload dominates, and entering your contract rate under custom rates makes estimates use it ahead of list. Budgets and commitment tracking work on your own OpenAI account; OpenAI keeps billing you directly for the inference.
