Gemini Omni Flash edit billed per input second vs Sume reserve

Runway bills its gemini_omni_flash video-to-video at 11 credits per second of input video, capped at 10 seconds, plus 1 credit per reference image (its pricing page lists the 1.1 model separately). Sume's gemini-omni-flash-1.1 edit is billed by output second at provider list times 1.25, and because the output length is not returned, the reserve uses a duration hint that defaults to 8 seconds.

Runway numbers are from its pricing guide; Sume's from the Video Router docs, read 2026-10-01.

How does Runway count an edit?

Per the guide, the unit is the input clip: 11 credits for each second of input, up to 10 seconds, and 1 credit for each reference image. A longer input does not raise the charge beyond the 10-second cap.

How does Sume reserve an edit?

An edit sends no duration to the provider and the output follows the source clip. If you pass duration with video_url, it is only the reserve-estimate hint, default 8 seconds. The provider does not return an output duration for edits, so the reserve is a hint, not a probe of your file.

What can go wrong with a hint?

The reserve is an estimate set before the job runs. If your clip is far from 8 seconds, set duration near the real length so the reserve is close; do not treat the hint as a quote. Check the job result for the amount billed.

What should I do?

Trim the source to what you need before sending, set duration to its length, and read per-model pricing rows from the model catalog. For per-resolution costs of the same model see Gemini Omni Flash 1.1 at 360p.