RETIRING IN 146 DAYS

Sunset scheduled for 2027-02-09, reported by a third-party catalog. The identifier still resolves today. Sources disagree on: context_tokens.

state=dying sunset=2027-02-09 days_remaining=146 severity=high sources=litellm,openrouter evidence_tier=catalog confirmed_by_endpoint=false documented_by_provider=false replacement=none corroborated=yes divergent_fields=context_tokens checked=2026-09-16 03:02Z

openai/gpt-5

Q: Is gpt-5 deprecated?

Not yet, but retirement is scheduled. Sunset scheduled for 2027-02-09, reported by a third-party catalog. The identifier still resolves today.

Vendor: openai. Tracked by 2 of 5 sources.

What each source reports

**endpoint** = the provider's own machine-readable API, the strongest evidence. **provider docs** = the provider's own documentation, read by a model — first-party content, inferred reading. Unlabelled rows are third-party catalogs. Where sources disagree both values are shown rather than silently reconciled.
Source	ID	Context	Max out	In $/Mtok	Out $/Mtok	Sunset
litellm	azure/gpt-5	272,000	128,000	$1.25	$10	2027-02-09
openrouter	openai/gpt-5	400,000	128,000	$1.25	$10	—

Change history

Severity	Change	What	Detected
medium	deprecated	azure/gpt-5: deprecation announced for 2027-02-09 — in 172 days	2026-08-21
medium	deprecated	azure/gpt-5: retires 2027-02-09 (in 172 days)	2026-08-21
info	modified	[source artifact — 6 providers changed identically on the same day] gpt-5: capabilities lost service_tier	2026-06-27