Skip to content
DriftCaught

Change log, by what changed

Pricing changes

A price change moves what your feature costs per request, not what it returns. It matters to any design that was tuned around the old numbers, such as how much context you send.

Rates or access terms moved. Behaviour did not, unless the provider also said so.

5 entries . window ends 2026-09-24

By provider

OpenAI
2
Google
2
Meta
1

Recommended action

Other views

Pricing changes over twelve months

Tracked provider changes, Oct 2025 to Sep 2026

Oct 2025Jan 2026Apr 2026Jul 2026OpenAIOpenAI, 21 August 2026, Pricing: gpt-5.6-solOpenAI, 30 July 2026, Pricing: gpt-5.6-sol, gpt-5.6-terra, gpt-5.6-lunaGoogleGoogle, 1 April 2026, Pricing: Flex, PriorityGoogle, 5 December 2025, Pricing: Grounding with Google SearchMetaMeta, 8 July 2026, Pricing: muse-spark-1.1
  • New version
  • Weight refresh
  • Deprecation
  • Pricing, context and tool changes share these three colours and always carry a label.
The same timeline as a list, 5 changes
  1. 2026-08-21 OpenAI, Pricing: gpt-5.6-sol
  2. 2026-07-30 OpenAI, Pricing: gpt-5.6-sol, gpt-5.6-terra, gpt-5.6-luna
  3. 2026-07-08 Meta, Pricing: muse-spark-1.1
  4. 2026-04-01 Google, Pricing: Flex, Priority
  5. 2025-12-05 Google, Pricing: Grounding with Google Search

Every entry

Pricing changes, newest first

OpenAIPricing

gpt-5.6-sol

OpenAI reduced GPT-5.6 Sol pricing to $4 per million input tokens and $20 per million output tokens. The entry states the reduced price is promotional through November 21.

Rerun the suiteUpdate the per token rates in your cost model and dashboards, and put the stated promotional end date in the budget calendar.

Source: OpenAI, OpenAI API changelog . verified 2026-09-22

OpenAIPricing

gpt-5.6-sol, gpt-5.6-terra, gpt-5.6-luna

OpenAI introduced Fast mode, which it describes as up to 2.5 times faster at twice the price. The entry also states that GPT-5.6 Luna costs 80 percent less and GPT-5.6 Terra 20 percent less.

Rerun the suitePrice the three GPT-5.6 tiers against your current spend per request, then run the cheaper tier through your suite before moving any traffic to it.

Source: OpenAI, OpenAI API changelog . verified 2026-09-22

MetaPricing

muse-spark-1.1

Meta put muse-spark-1.1 in public preview on the Meta Model API for United States developers, priced pay as you go at $1.25 per million input tokens and $4.25 per million output tokens. Meta lists end to end agentic workflows, advanced coding and native multimodal perception as the areas of improvement.

Rerun the suiteAdd the published input and output rates to your cost model, and note that the preview is limited to United States developers when you plan access.

Source: Meta, Build with Muse Spark, now available on Meta Model API . verified 2026-09-22

GooglePricing

Flex, Priority

Google introduced the Flex and Priority inference tiers, which it says offer more options for optimizing cost or latency.

Rerun the suitePrice your current traffic against both tiers, and run your suite on the tier you plan to move to before any traffic follows.

Source: Google, Gemini API changelog . verified 2026-09-22

GooglePricing

Grounding with Google Search

Google wrote that Gemini 3 billing for Grounding with Google Search would begin on January 5, 2026.

Rerun the suiteCount how many of your calls use Grounding with Google Search, and add the grounded request rate to your cost model.

Source: Google, Gemini API changelog . verified 2026-09-22

The full change log

Sources

Change-log entries restate provider announcements with sources and dates. Impact notes cite public practitioner reports. The site publishes no measurements of its own on any model.

Questions about pricing changes

How is a change classified as a pricing change?
From what the provider wrote, not from a guess about severity. Where a provider states that weights are unchanged, the entry is not classified as a weight change, and where an unchanged model string starts returning something else, it is.
Is this list complete?
It covers the model families we track for customers, inside a twelve-month window, where the announcement is reachable on the provider's own domain. Anything we cannot reach there is not published, however widely it was reported. Send us a provider link and we will add it.
Do you say what this did to real features?
No. The impact notes say what this kind of change typically touches, each citing a published practitioner source. What it did to your feature is a question only a rerun against your own dataset answers.

Related