Is gpt-4-32k-0613 deprecated?

Q: Is gpt-4-32k-0613 deprecated?

Yes — deprecated. Retired 2025-06-06 — 481 days ago. Requests to this identifier are expected to fail. The provider names gpt-4o as the replacement.

DEPRECATED

Retired 2025-06-06 — 481 days ago. Requests to this identifier are expected to fail. The provider names gpt-4o as the replacement.

state=dead sunset=2025-06-06 days_remaining=-481 severity=critical sources=docs,litellm evidence_tier=documentation confirmed_by_endpoint=false documented_by_provider=docs replacement=gpt-4o corroborated=yes divergent_fields=none checked=2026-09-30 15:40Z

openai/gpt-4-32k-0613

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	gpt-4-32k-0613	—	—	—	—	2025-06-06
litellm	azure/gpt-4-32k-0613	32,768	4,096	$60	$120	2025-06-06

Change history

Severity	Change	What	Detected
low	added	new model gpt-4-32k-0613	2026-09-25
info	deprecated	azure/gpt-4-32k-0613: deprecation announced for 2025-06-06 (date already passed)	2026-09-25
info	deprecated	azure/gpt-4-32k-0613: retires 2025-06-06 (476 days ago)	2026-09-25
medium	removed	[one catalog only — litellm still list it] gpt-4-32k-0613 is no longer listed by this source — calls to it are expected to fail	2026-09-24
info	deprecated	gpt-4-32k-0613: deprecation announced for 2024-06-06 (date already passed)	2026-08-05
info	deprecated	gpt-4-32k-0613: retires 2025-06-06 (421 days ago)	2026-08-01
low	added	new model gpt-4-32k-0613	2026-08-01