Veo 3.1 preview ids vs gemini-omni-1.1-flash vs Sume's Omni id

Three Veo 3.1 model ids map to one Google replacement, gemini-omni-1.1-flash, and the Sume catalog spells that model with the words in a different order: gemini-omni-flash-1.1. Copying the Google id into a Sume request is the easy mistake, so store the id you get from GET /v1/videos/models and do not retype it.

Google's ids and dates

The dates and replacement come from the Gemini API deprecations page. The prices come from the Gemini API pricing page (paid tier, per second of video).

The Sume spelling

Sume's video catalog uses bare ids with no provider prefix. The Sume docs say a model that is not a catalog id, an alias or sume/auto returns 404 model_not_found. The docs do not list the Google spelling as an alias, so use the id exactly as the catalog returns it.

Mapping table

Sume lists no Veo model. The Sume docs name Veo 3.1 as a family that is not in the v1 catalog.

Request body on Sume

A minimal Sume request for the replacement model looks like this. duration is a whole number of seconds from 3 to 10, and the aspect ratio is 16:9 or 9:16.

{
  "model": "gemini-omni-flash-1.1",
  "prompt": "A slow dolly shot across a wooden desk with a ceramic mug",
  "duration": 8,
  "resolution": "720p",
  "aspect_ratio": "16:9"
}