$1.00 scheduled run: a music bed, a narration and six images

One $1.00 scheduled run can make a music bed ($0.125), a 5,000-character voiceover ($0.2375) and six Nano Banana 2.1 images at 1K ($0.60) for $0.9625 in total. This mix is a weekly social post without any video clip, and it leaves $0.0375 under the default cap.

The budget line by line

Music on Sume is a flat $0.125 per generation. TTS is $0.0475 per 1,000 characters. Nano Banana 2.1 at 1K is $0.10 per image.

Run it from your own service

If the schedule has api_trigger_enabled, your key needs actions:write. A test run can pass a lower cap than the schedule's; the API takes the smaller of the two.

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

Everything the agent generates counts toward the cap, including retries. A seventh image would take the run to $1.0625, over the default.

• A schedule's events_url is always null, so poll status_url for progress.
• Skipped runs, which happen by default when a previous run is active, send no webhook.
• A cron schedule can also accept API runs when api_trigger_enabled is true.