What $5 buys on Gemini Omni Flash 1.1: clips by resolution

Five dollars buys 41 three-second Omni clips at 360p, or 13 ten-second clips at 360p, but only 4 three-second clips or a single ten-second clip at 4K. The resolution you pick changes the count by a factor of ten.

These are Sume prices for gemini-omni-flash-1.1: provider list rates of $0.03, $0.10, $0.15 and $0.30 per second times 1.25, with each clip rounded up to the cent (Video Router page).

Clips per $5

Counts below are whole clips, since a job either runs or it does not. Leftover change is not enough for another clip.

Reading the table

• The 3 second floor is the cheapest valid clip on this model; the length range is 3 to 10 seconds.
• 360p is 30 percent of the 720p rate, which is Sume's own ratio. Google's 360p draft claim of "a third of the cost" is for its standard 720p tier (Google blog, read 2026-10-05).
• 4K is exactly twice 1080p per second and 3 times the 720p rate.
• Per-clip rounding is a bigger factor at short lengths: a 3 s 360p clip is $0.1125 before rounding and $0.12 billed.

A split that uses the budget well

For a $5 test, one reasonable split is twelve 360p ten-second drafts ($4.56) plus nothing else, or ten 360p drafts ($3.80) and one 720p ten-second keeper ($1.25), which totals $5.05, just past the budget. Drop to nine drafts ($3.42) and the keeper fits at $4.67.

If you need sound-on tests, note that native audio is always on for this model and there is no mute toggle: the API rejects generate_audio: false, so every price above includes audio.

What the numbers are built from

The 360p tier is documented at a list price of $0.03 per second, 720p at $0.10, 1080p at $0.15 and 4K at $0.30. Sume multiplies each by 1.25 and rounds the clip up to the cent. A five-second clip is therefore $0.19, $0.63, $0.94 and $1.88 across the four tiers. Those are the same figures that a Video Router catalog read returns, so you can reproduce the table without trusting this page.

Read the catalog row for gemini-omni-flash-1.1 from GET /v1/video-router/models before a large run; capabilities and rates are carried on each row, and the row is the source of truth if it ever differs from a blog post.

Why the counts jump

The count of clips falls by about 3.3 times between 360p and 720p ($0.0375 to $0.125 per second) and then by smaller steps. The step from 720p to 1080p is 1.5 times, and from 1080p to 4K exactly 2 times. That is why a small budget stretches furthest by drafting and why a budget that must produce finals should be planned in finals, not in drafts.

A practical reading: if $5 must deliver three finished ten-second clips, 1080p fits ($5.64 for three is over, two is $3.76), so the budget really buys two finals plus about three drafts at 360p ($1.14). If it must deliver three, 720p is the tier ($3.75).

Rounding at small sizes

Because each clip rounds up to the next cent, many tiny clips cost slightly more than their unrounded sum. Fifty 3-second 360p clips are $6.00 billed, against $5.63 at the unrounded rate, a 7 percent difference. Longer clips lose less to rounding.

Check your balance first

Sume reserves the cost on submit and returns 402 insufficient_credits if the balance is below the reserve. Read GET /v1/balance before a batch so you know which row of the table you are in.

curl https://api.sume.com/v1/balance \
  -H "Authorization: Bearer $SUME_API_KEY"