Balance for a 40-clip Omni 4K batch: $150, reserved at submit

Sume's video docs say that at submit the platform reserves the provider list price times 1.25, and that usage.cost on the finished job is the billable amount. For a single clip that is a rounding detail. For a batch it decides whether the loop dies halfway: if you submit 40 jobs and the wallet only covers 30, the last ten are refused at submit and produce nothing.

The numbers below are for ten-second Gemini Omni Flash 1.1 clips, the model whose 4K price makes the reserve largest. Each job is rounded up to the cent.

Balance needed to submit the whole batch

Keep the loop from half-finishing

Sum the reserve first, compare it to the balance, and submit only if the batch fits. GET /v1/balance is the balance route named in Sume's docs. Pair every submit with an Idempotency-Key built from your own batch id, so a crashed script that restarts re-attaches to the jobs it already created instead of reserving them twice.

Draft at a lower tier when you are unsure. Forty 5-second drafts at 360p cost $7.60 in total, and rerunning ten winners as 10-second 4K clips adds $37.50, far less than $150.

Idempotent submit for one item

The key repeats across restarts. Change it only when you want a new generation of the same prompt.

curl -X POST https://api.sume.com/v1/videos \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: batch-2026-10-07-item-017" \
  -d '{"model":"gemini-omni-flash-1.1","prompt":"Slow orbit around a glass bottle on wet stone","duration":10,"resolution":"4K","aspect_ratio":"16:9"}'