Runway Gemini Omni Flash 1.1: 10 credits/s is $0.10/s, like Google

Runway's developer pricing guide (read 2026-10-02) lists gemini_omni_flash_1.1 at 720p as 10 credits per second plus 1 credit per reference image, and credits cost $0.01 each. That is $0.10 per second, which matches Google's own Gemini API pricing (read 2026-10-02): $17.50 per million video output tokens, which Google puts at about $0.10 per second of 720p video.

Three prices for the same second

The model is the same Google model in all three places. The difference is how each reseller or direct route turns it into a bill. Sume's rule from the video docs is that jobs reserve at provider list times 1.25; the list rate comes from GET /v1/videos/models, and Sume's Video Router lists gemini-omni-flash-1.1 at 3 to 10 seconds, with 360p, 720p, 1080p and 4K.

What the reference-image credit adds

The Runway line charges 1 credit, $0.01, per reference image. A 10-second clip with 3 reference images is 103 credits, $1.03. That is small against the clip, but it makes Runway's bill depend on how many references you send, where a pure per-second price does not.

Is the 25% worth it

On this model the direct routes are cheaper per second by the Sume margin, and the table shows it plainly: $1.25 versus $1.00 for the same 10 seconds. What the extra buys is not a different model but the surrounding job layer: a single USD wallet, an idempotent submit-and-poll API, per-job usage rows with reserved, captured and refunded states, and one invoice across every provider you call.

If you only ever call this one model, from one team, the direct route wins on price. If you mix models, or need a ledger you can reconcile per job, the margin is what you pay for it. The Sume figure in the table assumes a $0.10 list; confirm it against the catalog before you quote it.