Veo 3.1 Lite's id ends in -preview; Sume model ids are bare slugs

The Gemini API's Veo 3.1 Lite page gives the model id veo-3.1-lite-generate-preview, and marks the latest update as March 2026 (read 2026-10-04). That id carries a vendor suffix, generate-preview, that tells you it is a preview model.

If you ported a script from the Gemini API to Sume, do not carry the id across. The Sume Video Router names models by catalog slug: kling-3, wan-3.0, seedance-2, gemini-omni-flash-1.1. The slug is the id field returned by GET /v1/videos/models, per the video generation docs. Veo 3.1 Lite is not in that list, so sending the Google id returns an error rather than a clip.

Copy ids, do not type them

The safest pattern is to read the list and validate your choice before the first paid call.

import os
import requests

want = "wan-3.0"
resp = requests.get(
    "https://api.sume.com/v1/videos/models",
    headers={"Authorization": f"Bearer {os.environ['SUME_API_KEY']}"},
)
ids = [m["id"] for m in resp.json()["data"]]
if want not in ids:
    raise SystemExit(f"{want} not in catalog: {ids}")
print("ok", want)

Why it matters

A catalog id is part of your cost model. wan-3.0 bills $0.0625, $0.125 or $0.25 per second at 480p, 720p and 1080p, while gemini-omni-flash-1.1 bills $0.1875 at 1080p. A wrong id fails before any money is reserved, but a wrong guess about which model sits behind a familiar name can still blow a budget.