RETIRING IN 356 DAYS
Sunset scheduled for 2027-09-07, reported by a third-party catalog. The identifier still resolves today.
state=dying sunset=2027-09-07 days_remaining=356 severity=high sources=litellm evidence_tier=catalog confirmed_by_endpoint=false documented_by_provider=false replacement=none corroborated=single-source divergent_fields=none checked=2026-09-16 03:02Z
openai/gpt-5.4-pro-2026-03-05
Vendor: openai. Tracked by 1 of 5 sources.
What each source reports
| Source | ID | Context | Max out | In $/Mtok | Out $/Mtok | Sunset |
|---|---|---|---|---|---|---|
| litellm | azure/gpt-5.4-pro-2026-03-05 | 1,050,000 | 128,000 | $30 | $180 | 2027-09-07 |
Change history
| Severity | Change | What | Detected |
|---|---|---|---|
| info | repriced | gpt-5.4-pro-2026-03-05: cache_read_price_per_mtok $3.00/Mtok to n/a | 2026-09-13 |
| high | modified | gpt-5.4-pro-2026-03-05: capabilities lost minimal_reasoning_effort | 2026-09-11 |
| medium | deprecated | azure_ai/gpt-5.4-pro-2026-03-05: deprecation announced for 2027-09-07 — in 382 days | 2026-08-21 |
| medium | deprecated | azure_ai/gpt-5.4-pro-2026-03-05: retires 2027-09-07 (in 382 days) | 2026-08-21 |
| medium | deprecated | azure/gpt-5.4-pro-2026-03-05: deprecation announced for 2027-09-07 — in 391 days | 2026-08-12 |
| medium | deprecated | azure/gpt-5.4-pro-2026-03-05: retires 2027-09-07 (in 391 days) | 2026-08-12 |
| info | modified | [source artifact — 6 providers changed identically on the same day] azure_ai/gpt-5.4-pro-2026-03-05: capabilities lost service_tier | 2026-06-27 |
| info | modified | [source artifact — 6 providers changed identically on the same day] gpt-5.4-pro-2026-03-05: capabilities lost service_tier | 2026-06-27 |
| low | added | new model azure_ai/gpt-5.4-pro-2026-03-05 (1,050,000 ctx) | 2026-05-16 |