AI API changes: July 2026
5 changes shipped without an announcement, and 0 that came with a published date. Compiled automatically from provider catalogs and endpoints; every figure below links to the model it came from.
4
capacity cuts
context or output shrank
1
price changes
same call, different bill
0
capabilities lost
0
announced
deprecations with a date
Unannounced, biggest first
| Impact | Provider | What changed | Detected |
|---|---|---|---|
| truncation | fireworks_ai | -88% max out · fireworks_ai/accounts/fireworks/models/kimi-k2p5: max_output_tokens cut 262,144 to 32,768 +9 aliases inferred | 2026-07-31 |
| truncation | azure | -74% ctx · azure/gpt-5.4-mini-2026-03-17: context_tokens cut 1,050,000 to 272,000 +3 aliases | 2026-07-30 |
| truncation | openai | -74% ctx · gpt-5.4-mini-2026-03-17: context_tokens cut 1,050,000 to 272,000 +3 aliases | 2026-07-30 |
| cost | fireworks_ai | 1.86x price · fireworks_ai/accounts/fireworks/models/glm-5p2: cache_read_price_per_mtok $0.14/Mtok to $0.26/Mtok +1 alias | 2026-07-20 |
| truncation | azure_ai | -32% ctx · azure_ai/gpt-5.4-mini-2026-03-17: context_tokens cut 400,000 to 272,000 +3 aliases | 2026-07-30 |
Announced this period
| Impact | Provider | What changed | Detected |
|---|---|---|---|
| Nothing yet. | |||
Who changed the most
| Provider | Unannounced changes |
|---|---|
| fireworks_ai | 2 |
| azure | 1 |
| openai | 1 |
| azure_ai | 1 |