402 insufficient_credits on Sume: how much balance a video job needs

A 402 insufficient_credits from Sume means the workspace balance is not enough to reserve the estimated cost of the generation. The error docs list it as "The balance is not sufficient for the requested generation," and the admission docs say it is returned before provider work starts. Nothing is spent when you see it.

How much you need

You need at least the hold for the job, plus the holds of anything already in flight. For one video the hold is the provider list price times 1.25. These are the amounts from the repo's estimators for a single 5-second text-to-video request.

What to do when you get it

• Check the balance with GET /v1/balance and compare available_amount_usd_micros with the amount above.
• Cancel queued jobs you no longer want; cancellation works only before generation work starts.
• Submit a cheaper request: a lower resolution or a shorter duration.
• Read the next-action advice for quota job errors in the docs: add funds or decrease the request cost.

Reading the balance response

The balance endpoint returns a state of funded or empty, the spendable amount in USD micros and cents, and an expiry summary for credit lots. empty means no spendable balance or no balance row yet. For a 402 investigation, the micros field is the one to compare, since the hold is also in micros.

The generation-admission docs add that the way out is to upgrade the plan, wait for included Gen$, or submit a less expensive request, and that you should not invent prepaid top-ups. The credits page says a top-up is a dashboard action and that the public API has no endpoint for creating one.

A trap with parallel jobs

Ten 720p Wan clips in flight hold $6.25 together. If you have $5 spendable, the first eight succeed in being accepted and the ninth gets a 402, even though each job alone would fit. Retries should wait for earlier jobs to settle, and the idempotency key should stay the same so a replay does not create a second job.