Nano Banana 2.1 images per $1.00 scheduled run, by resolution

Under the $1.00 default cap of a Sume schedule, a run can make 13 Nano Banana 2.1 images at 0.5K, 10 at 1K, 6 at 2K, or 5 at 4K. Google lists Nano Banana 2.1 as generally available since Oct 6 2026 (Gemini API changelog, read 2026-10-09); the Sume prices below are what a schedule pays.

Images per dollar

Image prices are flat per image at each resolution. Dividing the $1.00 cap by the price and rounding down gives the count; the total shows how much of the cap is left.

Shaping the instruction

A schedule runs stored instructions, so the count has to be in the instructions, not guessed by the agent. State the resolution and the number of images, and send a lower cap on an API-triggered test run to see that the count holds:

curl -sS -X POST "https://api.sume.com/v1/actions/$ACTION_ID/runs" \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"generation_spend_cap_usd": 0.5}'

Limits and gotchas

The cap bounds generation spend, and image count is only one use of it. If the same run also makes narration or music, those prices come out of the same $1.00.

• A per-run cap can only lower the schedule cap, never raise it.
• The 2K row leaves $0.10, which is not enough for another 2K image at $0.15.
• Nano Banana 2.1 is also available over the API with aspect ratios such as 1:4 and 8:1; see the image model page before you promise a ratio.