Minimum balance to submit a 10-second AI video job

Your balance must cover the job's estimate at the moment you submit. For a 10-second clip that is $0.125 on Grok Imagine Video 1.5, $1.25 on Wan 3.0 at 720p and $3.75 on Gemini Omni Flash 1.1 at 4K. If the balance is short, the request returns 402 insufficient_credits before provider work starts.

Reserve for one 10-second job

Estimates are the Sume billable per-second rate times 10 seconds.

Check before you submit

Read the balance first. The response shape is documented in the OpenAPI reference, so this example only shows the call.

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

What happens next

The estimate is reserved at submit. A success captures it. A failure, or a cancel before the job starts, releases or refunds it. Because the hold uses the same estimate that billing uses, the minimum balance for one job is the job's price, not a different safety figure.

• Several jobs in flight hold several estimates at once.
• A run with a generation spend cap stops when the cap is reached, whatever the balance.

Worked example: a batch of five

Five 10-second Wan 3.0 jobs at 720p reserve $1.25 each, so $6.25 is held while they run. If three succeed and two fail, $3.75 is captured and $2.50 returns to the balance. Your free balance must cover all five holds, $6.25, by the time you submit the fifth job, or that request alone returns 402.

If you submit them one at a time and wait, you only ever need $1.25 free. Parallelism costs working capital, not extra money.

Limits

A balance that is exactly enough for one job is not enough for a second submitted before the first finishes. The tables show the model amount. A workspace Agent Fee line can be added on top, so treat the job's own usage cost as the truth and check the live catalog before you budget; limits and rows change.