Is gpt-4o-2024-08-06 deprecated?

Q: Is gpt-4o-2024-08-06 deprecated?

Yes — deprecated. Retired 2026-02-27 — 156 days ago. Requests to this identifier are expected to fail.

DEPRECATED

Retired 2026-02-27 — 156 days ago. Requests to this identifier are expected to fail. Sources disagree on: input_price_per_mtok, output_price_per_mtok.

state=dead sunset=2026-02-27 days_remaining=-156 severity=critical sources=litellm,openrouter evidence_tier=catalog confirmed_by_endpoint=false documented_by_provider=false replacement=none corroborated=yes divergent_fields=input_price_per_mtok,output_price_per_mtok checked=2026-08-02 01:41Z

openai/gpt-4o-2024-08-06

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/eu/gpt-4o-2024-08-06	128,000	16,384	$2.75	$11	2026-02-27
openrouter	openai/gpt-4o-2024-08-06	128,000	16,384	$2.5	$10	—

Change history

Severity	Change	What	Detected
info	deprecated	azure/eu/gpt-4o-2024-08-06: retires 2026-02-27 (155 days ago)	2026-08-01
info	deprecated	azure/global-standard/gpt-4o-2024-08-06: retires 2026-02-27 (155 days ago)	2026-08-01
info	deprecated	azure/global/gpt-4o-2024-08-06: retires 2026-02-27 (155 days ago)	2026-08-01
info	deprecated	azure/gpt-4o-2024-08-06: retires 2026-02-27 (155 days ago)	2026-08-01
info	deprecated	azure/us/gpt-4o-2024-08-06: retires 2026-02-27 (155 days ago)	2026-08-01
info	modified	[source artifact — 6 providers changed identically on the same day] gpt-4o-2024-08-06: capabilities lost service_tier	2026-06-27