RETIRING IN 64 DAYS

Sunset scheduled for 2026-11-19, reported by a third-party catalog. The identifier still resolves today.

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

openai/o3

Q: Is o3 deprecated?

Not yet, but retirement is scheduled. Sunset scheduled for 2026-11-19, 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/o3	200,000	100,000	$2	$8	2026-11-19
openrouter	openai/o3	200,000	100,000	$2	$8	—

Change history

Severity	Change	What	Detected
high	deprecated	azure/o3: deprecation announced for 2026-11-19 — in 67 days	2026-09-13
high	deprecated	azure/o3: retires 2026-11-19 (in 67 days)	2026-09-13
low	added	new model openrouter/openai/o3 (200,000 ctx)	2026-09-06
high	deprecated	azure/o3: deprecation announced for 2026-10-21 — in 61 days	2026-08-21
high	deprecated	azure/o3: retires 2026-10-21 (in 61 days)	2026-08-21
info	modified	[source artifact — 6 providers changed identically on the same day] o3: capabilities lost service_tier	2026-06-27