Stocking-stuffer gift videos: a bigger spend cap for the hero SKU only

Yes, you can set a different spend ceiling per item in a Sume bulk queue. Each item is the same body as a single run, so generation_spend_cap_usd goes on the item, and a hero gift and forty small ones do not have to share one number.

How the cap resolves

A tiered batch

The cap is a ceiling on that run's generation spend, not a price. usage.billable_amount_usd_micros on the receipt reports the actual spend against it. Because each item carries its own cap and the queue body has no total-spend field, the worst case is the sum of the item caps, so size them deliberately.

def item(sku, hero=False):
    return {
        "instruction": "Gift idea video, 9:16, warm light.",
        "input": {"sku": sku, "under_usd": 25},
        "generation_spend_cap_usd": 60 if hero else 15,
    }

items = [item("HERO-1", hero=True)] + [item(f"STUF-{i}") for i in range(39)]
body = {"concurrency": 8, "items": items}
# worst case bound: 60 + 39 * 15 = 645 USD

What a low cap means

A run cannot spend past its own cap, so a cap that is too low can leave a run unable to finish. Test a handful at the cap you plan, read usage on the receipts, then set the queue's numbers. A single-scene retry on the same thread needs a fraction of the original run's budget, so retries can use a smaller cap.