OpenAI: the pricing arc

The SPP read

OpenAI updated its Enterprise pricing page to formally disclose that both token-based and credit-based billing are available on Enterprise plans, marking a structural clarification of which units buyers may be metered on at that tier. Separately, a listed model was removed from the Business and Enterprise plan feature matrix, narrowing the visible access set for those tiers. A feature row was also relabeled, repositioning how the capability is surfaced to buyers without a stated change to underlying limits.

The SPP read

One announcement, three prices. On July 30, 2026 OpenAI cut GPT-5.6 Luna by 80 percent, to $0.20 per million input tokens and $1.20 per million output, trimmed GPT-5.6 Terra 20 percent to $2 and $12, and added a Fast mode for Sol. The headline write-ups carried Luna's number; the card carried all three. The cheap tier got radically cheaper while the flagship edged down, which is what a price-performance frontier looks like when a vendor moves the whole curve at once.

The SPP read

GPT-5.6 launched July 9 with Sol as the new flagship at $5 per million input and $30 output on short context, the same list price as the GPT-5.5 it superseded; OpenAI positioned Terra, at half that, as the 5.5 analog. The August 22 move is what makes this an arc event: Sol's price went on a clock. The developer pricing page now lists $4 and $20 with the line 'GPT-5.6 Sol's promotional pricing is available at least through November 21, 2026.' A discount with a published end date is a promotion, not a price cut, and its withdrawal is an increase nobody has to announce. Google shipped the same instrument in the same window, with Gemini prices that revert on January 1, 2027.

The SPP read

One announcement, three named rungs: a small tier at a fraction of the mid, a mid at half the top, and the top holding the flagship rate. Model families used to ship as one price with a mini beside it; this ships as a designed ladder, and the design is the point. Named rungs give the meter a packaging layer: buyers self-sort by workload instead of negotiating, and the vendor gains rungs it can move independently later. The ledger shows that option getting exercised within weeks, when the bottom rung was cut by four fifths and the middle trimmed while the top held. A ladder is the set of places a future price change can land without touching the others, and this vendor built one on purpose.

The SPP read

A six-to-one output premium puts the price on generation, not context. For application vendors pricing on top of the API, the asymmetry matters more than the headline rate, because features that read long and write short carry a different unit cost than features that write long. Blended per-request pricing built on an average mix breaks the day the mix shifts. Price the direction your workload actually spends.

The SPP read

An 80% cut on the reasoning model, announced the same day a pro variant arrived at ten times the new rate, is one decision expressed as two prices. The cut moves the base model toward commodity territory and the simultaneous premium launch preserves somewhere for the spend to go. Vendors under capability deflation keep doing this: the price of last year's frontier falls fast, and a new rung appears above it so the falling floor never takes the ceiling down with it. Watch the gap between rungs rather than either price alone; the gap is the actual product strategy.