Is veo-3.1-generate-001 deprecated?

Q: Is veo-3.1-generate-001 deprecated?

Not yet, but retirement is scheduled. Sunset scheduled for 2026-11-17, reported by a third-party catalog. The identifier still resolves today.

RETIRING IN 17 DAYS

Sunset scheduled for 2026-11-17, reported by a third-party catalog. The identifier still resolves today.

state=dying sunset=2026-11-17 days_remaining=17 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-10-31 05:09Z

google/veo-3.1-generate-001

Vendor: google. 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	vertex_ai/veo-3.1-generate-001	1,024	—	—	—	2026-11-17

Change history

Severity	Change	What	Detected
high	deprecated	vertex_ai/veo-3.1-generate-001: deprecation announced for 2026-11-17 — in 88 days	2026-08-21
high	deprecated	vertex_ai/veo-3.1-generate-001: retires 2026-11-17 (in 88 days)	2026-08-21