20 Omni Flash 1.1 clips in one jobs_wait wave: $12.50 at 720p

Twenty 5-second Gemini Omni Flash 1.1 clips at 720p cost $12.50 on Sume ($0.625 each) and fit one jobs_wait call of 20 ids. Cost table and the call body.

4 min readSume
All posts

Twenty 5-second Gemini Omni Flash 1.1 clips at 720p cost $12.50 on Sume ($0.125 per second, $0.625 per clip), and the 20 job ids fit one jobs_wait call, the documented maximum. With include_results: true, the same call returns each finished clip, so a wave needs no separate result read.

Cost of the wave

Totals are per-second rate times seconds times clips.

20 Omni Flash 1.1 clips of 5 s (read 2026-10-09)
ResolutionRate per secondOne clip (5 s)20 clips
360p$0.0375$0.1875$3.75
720p$0.125$0.625$12.50
1080p$0.1875$0.9375$18.75

Submit, then wait once

Each create is its own paid call and needs its own idempotency_key (and a max_spend_usd of $0.625 if you want a per-call ceiling). After the 20 creates, one wait covers the wave:

{
  "job_ids": ["job_01", "job_02", "...", "job_20"],
  "wait_for": "all",
  "include_results": true
}

Limits and gotchas

One call holds at most 55 seconds, so a wave usually needs more than one wait. Repeat the same ids on wait_slice_expired.

  • results_omitted.job_ids names results too big for one answer; read them with one batch jobs_result.
  • max_spend_usd guards one call, not the 20-call total.
  • script_run can issue many creates in one tool call, bounded by max_paid_calls.

Sources

Related posts

More in Developers

All Developers posts

Written by Sume