Is grok-4-0709 deprecated?

Q: Is grok-4-0709 deprecated?

Yes — deprecated. Retired 2026-05-15 — 124 days ago. Requests to this identifier are expected to fail.

DEPRECATED

Retired 2026-05-15 — 124 days ago. Requests to this identifier are expected to fail.

state=dead sunset=2026-05-15 days_remaining=-124 severity=critical sources=litellm evidence_tier=catalog confirmed_by_endpoint=false documented_by_provider=false replacement=none corroborated=single-source divergent_fields=none checked=2026-09-16 03:02Z

xai/grok-4-0709

Vendor: xai. Tracked by 1 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	xai/grok-4-0709	256,000	256,000	$1.25	$2.5	2026-05-15

Change history

Severity	Change	What	Detected
info	repriced	xai/grok-4-0709: input_price_per_mtok $3.00/Mtok to $1.25/Mtok	2026-08-30
info	repriced	xai/grok-4-0709: output_price_per_mtok $15.00/Mtok to $2.50/Mtok	2026-08-30
info	repriced	xai/grok-4-0709: cache_read_price_per_mtok n/a to $0.20/Mtok	2026-08-30
info	deprecated	xai/grok-4-0709: retires 2026-05-15 (78 days ago)	2026-08-01
info	deprecated	xai/grok-4-0709: deprecation announced for 2026-05-15 (date already passed)	2026-06-05