Balance to submit 10-second Omni jobs: $0.375 to $3.75 reserved each

A 10-second gemini-omni-flash-1.1 job reserves $0.375 at 360p, $1.25 at 720p, $1.875 at 1080p and $3.75 at 4K from your Sume workspace balance when you submit it. The Sume docs say that at submit Sume reserves the provider list times 1.25, and that usage.cost on the poll response is the billable amount. So a batch of jobs needs the sum of their reserves available at the moment you submit them, not at the moment they finish.

Reserve per job and per batch

The per-second rates are $0.0375, $0.125, $0.1875 and $0.375 at the four resolutions, which are the provider list prices of $0.03, $0.10, $0.15 and $0.30 times 1.25. Omni accepts clips of 3 to 10 seconds, so 10 seconds is the largest single reserve. The table shows one job and then batches of 10 and 50 submitted together.

Why this matters for a script

A script that fires 50 jobs at 4K in a loop is asking for $187.50 of balance at once. Google prices Omni by output token, and Sume's reserve is a separate Sume ledger step. On Sume you can read what happened with GET /v1/usage, which the API reference describes as listing reservations, captures, refunds and top-ups.

The practical rule is to submit in waves sized to your balance, and top up before a large run. Do not fire a 4K batch on a balance sized for 720p.

Checking the number before you run

Submit one job, wait for it, and read usage.cost. If it matches the table, multiply by the number of jobs you plan. If your job is shorter, scale: a 6-second 4K clip is 6 x $0.375 = $2.25, a 3-second one is $1.125. Keep the per-job Idempotency-Key stable across retries so you do not hold a second reserve for the same request.

• Reserve at submit: provider list x 1.25 per output second.
• Billable amount: usage.cost on the poll response.
• Ledger: GET /v1/usage for reservations, captures, refunds and top-ups.

What to do when the batch is bigger than the balance

Split it. Run the drafts at 360p first, where a 10-second job holds $0.375, then run only the approved shots at a higher resolution. Fifty 360p drafts hold $18.75 in total; five 4K finals hold $18.75 too, which is a useful symmetry when you size a balance for a round of review.

Rounding and refunds

Sume rounds a job's billable amount up to a whole cent, so a 3-second 360p job, which is 3 x $0.0375 = $0.1125, shows as $0.12. The reserve is a hold, and the ledger records the capture and any refund when the job finishes or fails. Read the ledger after the first wave to confirm that held amounts are released as expected.

If a submit is refused for lack of balance, nothing has been generated and nothing has been charged. Top up, then retry with the same Idempotency-Key.