Gemini Omni Flash 1.1 on Runway: 3.4 credits at 480p vs Sume's 360p

Runway's API pricing guide lists Gemini Omni Flash 1.1 at 3.4, 10, 15 and 30 credits per second, plus references, for four tiers. At $0.01 per credit that is $0.034, $0.10, $0.15 and $0.30 per second. Sume bills $0.0375, $0.125, $0.1875 and $0.375 per second for the same model family. Runway's lowest tier is labeled 480p, and Sume's lowest is 360p, so the first rows do not line up.

Per-second rates by tier

Runway values are from its API pricing guide. Sume values are the fal list rate times 1.25. Google's own price is about $0.10 per second of 720p video.

Where $0.10 comes from

Google's pricing page states video output at $17.50 per 1M tokens, and about $0.10 per second of 720p video at 5,792 tokens per second. The check: 5,792 x $17.50 / 1,000,000 = $0.10136, which rounds to $0.10. So Runway's 720p row equals Google's rate, and Sume's row is that list rate times 1.25.

A 10 second clip

The Sume rate for a 10 second clip is a straight multiple of the second price. At 720p it is 10 x $0.125 = $1.25, against $1.00 on Runway before references. At 4K it is 10 x $0.375 = $3.75 on Sume against $3.00 on Runway.

Runway's "plus refs" has no number in the guide I read, so I cannot total a request that uses reference media. On Sume, the Omni rate card prices output seconds by resolution tier; the model accepts up to 10 reference images and 3 reference clips of 3 seconds or less.

Which to choose

Runway is lower per second on every tier where both list a price. The difference is the Sume margin of 25% on top of the fal list. Sume offers the 360p tier at $0.0375, which Runway does not list.