Is o3-2025-04-16 deprecated?

Q: Is o3-2025-04-16 deprecated?

Yes — deprecated. Retired 2026-04-16 — 108 days ago. Requests to this identifier are expected to fail. The provider names gpt-5.6-sol as the replacement.

DEPRECATED

Retired 2026-04-16 — 108 days ago. Requests to this identifier are expected to fail. The provider names gpt-5.6-sol as the replacement.

state=dead sunset=2026-04-16 days_remaining=-108 severity=critical sources=docs,litellm evidence_tier=documentation confirmed_by_endpoint=false documented_by_provider=docs replacement=gpt-5.6-sol corroborated=yes divergent_fields=none checked=2026-08-02 01:41Z

openai/o3-2025-04-16

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
docs	o3-2025-04-16	—	—	—	—	2026-12-11
litellm	azure/o3-2025-04-16	200,000	100,000	$2	$8	2026-04-16

Change history

Severity	Change	What	Detected
medium	deprecated	o3-2025-04-16: retires 2026-12-11 (in 132 days)	2026-08-01
info	deprecated	azure/o3-2025-04-16: retires 2026-04-16 (107 days ago)	2026-08-01
info	deprecated	azure/us/o3-2025-04-16: retires 2026-04-16 (107 days ago)	2026-08-01
low	added	new model o3-2025-04-16	2026-08-01
info	modified	[source artifact — 6 providers changed identically on the same day] o3-2025-04-16: capabilities lost service_tier	2026-06-27