Is glm-5-turbo deprecated?

Q: Is glm-5-turbo deprecated?

Not yet, but retirement is scheduled. Sunset scheduled for 2098-12-31, reported by a third-party catalog. The identifier still resolves today.

RETIRING IN 26404 DAYS

Sunset scheduled for 2098-12-31, reported by a third-party catalog. The identifier still resolves today. Sources disagree on: context_tokens.

state=dying sunset=2098-12-31 days_remaining=26404 severity=high sources=litellm,openrouter evidence_tier=catalog confirmed_by_endpoint=false documented_by_provider=false replacement=none corroborated=yes divergent_fields=context_tokens checked=2026-09-16 03:02Z

zhipu/glm-5-turbo

Vendor: zhipu. 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	novita/zai-org/glm-5-turbo	202,800	131,072	$1.2	$4	—
openrouter	z-ai/glm-5-turbo	202,752	131,072	$1.2	$4	2098-12-31

Change history

Severity	Change	What	Detected
medium	deprecated	z-ai/glm-5-turbo: retirement announced for 2098-12-31 — in 26409 days	2026-09-11
low	added	new model openrouter/z-ai/glm-5-turbo (202,752 ctx)	2026-09-06
low	added	new model novita/zai-org/glm-5-turbo (202,800 ctx)	2026-08-28
medium	deprecated	z-ai/glm-5-turbo: retires 2098-12-31 (in 26450 days)	2026-08-01