Budget for 100 videos: 60 drafts, 30 at 720p, 10 at 1080p, 8 s each

A mixed set of 100 eight-second Omni Flash videos, 60 at 360p, 30 at 720p and 10 at 1080p, costs $63.00 on Sume. Making all 100 at 1080p would cost $150.00, so a tiered plan saves $87.00.

The tiered budget

Sume bills the provider list rate multiplied by 1.25 on every video model (Video Router). The figures here come from the price estimators in Sume's repository, run on 2026-10-07, and are rounded to the cent. The live numbers for your workspace are in the catalog response and on the API pricing page.

Why tiers beat a flat render

Most clips in a test never ship. Rendering them at 360p costs a quarter to a fifth of the final price, and the selection happens on the cheap tier. The numbers above assume 10 percent of drafts reach the final; if 20 do, raise the 1080p line to 20 clips and the total becomes $68.00.

Omni Flash 1.1 offers 360p, 720p, 1080p and 4K, 3 to 10 seconds (Video Router), so all three tiers are one model with one prompt format.

• A rerun is a new take, so a 360p draft shows the idea, not the exact final frames.
• Keep a 20 percent reserve for rejected takes.
• Total needed in the wallet at the peak is only the jobs in flight.

Run it safely

Sume reserves the estimated amount when it accepts a job, captures it on success, and refunds the reservation if the job fails or is cancelled before capture (Usage, Generation admission). So the balance you need on hand at submit time is the price of everything in flight, not only the final total.

A Pro workspace runs 4 jobs at once, Startup 8 and Scale 20 (the plans page lists the ladder), so a big batch drains in waves rather than all at once.

Set a cap before you start: from MCP, a paid tool takes dry_run=true and max_spend_usd (MCP tools and gates). Send a distinct Idempotency-Key per job so a retry replays the original job instead of charging again.

Check the figures against your own account

Every number on this page comes from the model rates and the 1.25 multiplier above, so you can reproduce it with a calculator. The live record is your own ledger: after a first job, read the balance and the usage rows for that job and compare the captured amount with the table. If they differ, trust the ledger and the model list your account returns, because the rates in the API response are the ones that bill.

The balance call below needs only an API key from your workspace and prints the USD balance. It does not start a job and costs nothing.

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

What these figures leave out

The prices here cover video generation only. Voice, captions, a Timeline join, storage and the plan fee are separate lines, and the API pricing page lists them. Taxes are not included. Provider list rates can change, and Sume applies the current published rate at submit, so a quote from last month is not a promise.

Retakes are the largest hidden cost in any batch. Add a reserve of 20 to 30 percent for clips you reject, and use cheaper settings for exploration before you spend at the final size. For this page's question, that rule turns the table into a floor rather than a forecast.