Is deepseek-v3.2-speciale deprecated?

Q: Is deepseek-v3.2-speciale deprecated?

No — still supported. Listed by litellm. No retirement date announced. Neither the provider's API nor its documentation has been checked for this model.

NOT DEPRECATED

Listed by litellm. No retirement date announced. Neither the provider's API nor its documentation has been checked for this model.

state=alive sunset=none days_remaining=n/a severity=low sources=litellm evidence_tier=catalog confirmed_by_endpoint=false documented_by_provider=false replacement=none corroborated=single-source divergent_fields=none checked=2026-09-30 15:40Z

deepseek/deepseek-v3.2-speciale

Vendor: deepseek. 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	azure_ai/deepseek-v3.2-speciale	128,000	128,000	$0.58	$1.68	—

Change history

Severity	Change	What	Detected
high	modified	azure_ai/deepseek-v3.2-speciale: context_tokens cut 163,840 to 128,000	2026-09-28
high	modified	azure_ai/deepseek-v3.2-speciale: max_output_tokens cut 163,840 to 128,000	2026-09-28