What can a $5 generation spend cap make? Clips, stills, captions

Agent Completions require generation_spend_cap_usd on every call; there is no default (Agent Completions). That is a feature: the caller has to decide what a request may spend. The practical question is what a number like $5 actually covers, because some prompts cannot finish under it.

The table prices common items from the Sume rate card read on 2026-10-03 and divides $5 by each price. Each row is one kind of item on its own, not a mix.

What does $5 cover?

A request can spend up to its cap and not beyond it. An item whose own price is above the cap cannot be generated within it, so the Seedance 2.5 clip at 720p and 15 seconds ($8.667) needs a larger cap.

How do you choose a cap for a mixed request?

Add the planned items and a margin. A request for six 5-second Wan 3.0 clips at 720p and six captions is 6 x $0.625 + 6 x $0.20 = $4.95, which is just under $5 and leaves almost nothing for a retry. Set the cap at $7 or $8 and the agent has room to regenerate one clip.

Remember that image prices differ by a factor of 37.5 between higgsfield-soul ($0.005) and nano-banana-pro ($0.1875). If a prompt lets the agent choose the model, a cap of $5 bounds the damage; if you pin the model, you can size the cap from the table.

Where does the cap stop?

The cap bounds generation spend for that request. It does not replace the wallet: if the balance cannot cover a job's reserve, the job returns 402 insufficient_credits. For schedules, the scheduled-run default cap is $1.00, which is a fifth of this table's budget.