Runway Aleph 2: 28 credits a second, 56 minimum, so 1 s costs $0.56

Runway's API bills Aleph 2 at 28 credits per second with a minimum of 56 credits per generation. At $0.01 per credit, that is $0.56 for a 1 second edit, and still $0.56 for 2 seconds. The price per second applies from 2 seconds up. On Sume, the video-edit route is gemini-omni-flash-1.1 with a video_url, and it reserves for 8 seconds at 720p unless you send a shorter hint.

Aleph 2 cost by edit length

Runway API figures are from the pricing guide. The web plan figure, 140 credits per 5 seconds, is from Runway's pricing page, and it equals 28 credits per second.

How the Omni edit is priced on Sume

The Sume Video Router docs say that an edit sends no duration to the provider, because the source clip sets the output length. If you send duration with video_url, it is only the reserve estimate, and the default is 8 seconds. The Sume rate card says edit bills output seconds, with the caller's duration hint, else 8 seconds. The resolution default is 720p. fal does not return an output duration, so the reserve is a hint and not a measured length.

What the numbers do and do not say

These two are not the same product. Aleph 2 is Runway's model, with its own quality and its own length handling. The Omni edit is Google's model through Sume. This post compares billing rules, not output quality, and I make no quality claim for either.

Other Sume edit routes

For a person swap, Sume has a separate model: h3-max-recast takes a source video of 5 to 30 seconds and 1 to 4 person photos. Its rate card is $0.30 per second at 768p and $0.45 at 1080p, which Sume bills at $0.375 and $0.5625 per second. The minimum source is 5 seconds, so the lowest cost is 5 x $0.375 = $1.875 at 768p.

Edits to short clips are where Runway's 56-credit floor bites: a 1 second Runway edit costs the same as a 2 second one. If your edits are short and frequent, count the minimum, not the per-second rate.