RETIRING IN 150 DAYS

Sunset scheduled for 2027-03-30, reported by a third-party catalog. The identifier still resolves today.

state=dying sunset=2027-03-30 days_remaining=150 severity=high sources=litellm evidence_tier=catalog confirmed_by_endpoint=false documented_by_provider=false replacement=none corroborated=single-source divergent_fields=none checked=2026-10-31 05:09Z

amazon/v3

Q: Is v3 deprecated?

Not yet, but retirement is scheduled. Sunset scheduled for 2027-03-30, reported by a third-party catalog. The identifier still resolves today.

Vendor: amazon. 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	deepseek.v3-v1:0	128,000	8,000	$0.58	$1.68	2027-03-30

Change history

Severity	Change	What	Detected
high	modified	deepseek.v3-v1:0: context_tokens cut 163,840 to 128,000	2026-10-08
high	modified	deepseek.v3-v1:0: max_output_tokens cut 81,920 to 8,000	2026-10-08
medium	deprecated	deepseek.v3-v1:0: deprecation announced for 2027-03-30 — in 173 days	2026-10-08
medium	deprecated	deepseek.v3-v1:0: retires 2027-03-30 (in 173 days)	2026-10-08