Runway Aleph 2 at $0.28/s vs Sume's Gemini Omni edit cost
Runway lists aleph2 at 28 credits a second; a 10 second edit is $2.80. Sume's gemini-omni-flash-1.1 edit bills $0.125 a second at 720p; here is the clip math.

Editing a 10 second clip with Runway's aleph2 costs $2.80, because Runway's API pricing guide lists it at 28 credits per second and credits at $0.01. The Sume counterpart is gemini-omni-flash-1.1 in video_to_video mode, which bills output seconds at the provider list times 1.25 by resolution: $0.125 per second at 720p, so $1.25 for 10 seconds, with one catch about duration spelled out below.
The two are not the same tool. Aleph 2 and Gemini Omni Flash edit differently and the pages do not give comparable quality claims, so this is a budget comparison only.
Price per second and per clip
Sume's per-second figures come from the fal list for Gemini Omni Flash 1.1 ($0.03, $0.10, $0.15 and $0.30 per second at 360p, 720p, 1080p and 4K) times 1.25.
| Option | Per second | 5 seconds | 10 seconds |
|---|---|---|---|
| Runway aleph2 | $0.28 | $1.40 | $2.80 |
| Sume gemini-omni-flash-1.1, 360p | $0.0375 | $0.1875 | $0.375 |
| Sume gemini-omni-flash-1.1, 720p | $0.125 | $0.625 | $1.25 |
| Sume gemini-omni-flash-1.1, 1080p | $0.1875 | $0.9375 | $1.875 |
The duration catch on Sume
Sume's docs describe the edit request as video_url plus a prompt, with resolution optional (default 720p) and no aspect_ratio or duration field. The pricing code explains why that matters: fal takes no duration on the edit endpoint, so the estimator bills an edit as output seconds using a caller duration hint where one exists, and otherwise 8 seconds. At the 720p default, an edit reserved at 8 seconds is 8 x $0.125 = $1.00, whatever the source length.
So for a 3 second source clip the 8 second default means you may reserve $1.00 for a clip whose seconds-based price is $0.375. For short fixes, check the reserve against usage.cost on your first job before you queue a batch.
Twenty edits
Twenty 10 second edits are 20 x $2.80 = $56.00 on aleph2 by Runway's per-second figure. On Sume at the 720p default and the 8 second billing basis they reserve 20 x $1.00 = $20.00, or 20 x $1.25 = $25.00 if your sources are 10 seconds and the hint is honored.
Edits keep the source aspect ratio and cannot be combined with image_url or reference_*_urls, per the Video Router docs. If you need to swap a person rather than edit a scene, a different Sume id (h3-max-recast) is priced per source second instead.
Sources
Related posts
More in Comparisons
- Runway gen4.5 API: 12 credits a second, a 10 s clip costs $1.20
Runway's API page prices gen4.5 at 12 credits a second at $0.01 a credit. A 10 second clip is $1.20; compared with Sume ids on the catalog.
- Runway Model Router credit ceiling vs Sume max_spend_usd
Runway's per-modality credit ceiling removes costly models before ranking and errors if none fit. Sume's max_spend_usd caps one call. How the two caps differ.
- Runway Model Router dryRun: preview the pick, and what Sume Auto shows
Runway's Model Router has a dryRun preview, per-modality credit ceilings and cost, latency or quality goals. Sume's sume/auto never says which family ran.
- Runway Model Routers report the model used; Sume Auto does not
Runway says router generations bill at the selected model's rate and report the model and cost. Sume's sume/auto never discloses which family ran.
Written by Sume