One prompt across video models: what to rewrite on Sume

A prompt that works on one Sume video row may need edits on another: Omni uses IMAGE_REF tokens, Kling takes no references, Veo is text-only. Read 2026-10-13.

5 min readSume
All posts

Reuse the scene text, but rewrite the parts tied to inputs. Three differences matter on Sume: Omni addresses references by token in the prompt, kling-3 rejects reference inputs, and the Veo rows accept a prompt and nothing else. A prompt sent to a row that cannot honor its inputs fails with 400 unsupported_capability; it is not silently reduced.

What to change per row

Keep the scene, subject and camera wording stable and vary only these items.

Prompt-side differences, from the Sume Video Router docs, read 2026-10-13.
RowChange
gemini-omni-flash-1.1Refer to inputs as <IMAGE_REF_0>, <VIDEO_REF_0> (counted from zero)
kling-3Drop references; supply a first frame instead
veo-3.1 rowsText only; drop every image or clip
wan-3.0, H3 rowsReferences go in input_references; no tokens documented
Any rowClamp duration to the row range

A safe test loop

Start with a 4 or 5 second clip at the lowest tier per row. Compare only the things you changed on purpose. Once a prompt passes on two rows, widen it to the long version. This also keeps the cost of a mismatch low, since each failed request fails before generation.

Sources

Related posts

More in Developers

All Developers posts

Written by Sume