Flow Agent makes several video variations at once: the API way
Google Flow's Agent toggle can create multiple variations of a video in one ask. Sume has no agent toggle in its API; it has queued jobs and Format bulk runs.

Yes: in Google Flow you switch on the Agent toggle in the prompt box and ask it for several variations of a video in one request (Flow Help, read 2026-10-02). Sume's API has no agent toggle, so the same outcome takes either several video jobs or one Format bulk run. This page maps the Flow behaviour onto those two Sume paths.
What Flow documents
Flow's help page says you activate the Agent by toggling Agent in the prompt box, and that you can ask it to create multiple variations of a video at once (read 2026-10-02). The page does not state a maximum number of variations or a credit cost for them, so this post does not either.
| Item | What the Flow page says |
|---|---|
| Switch | Toggle Agent in the prompt box |
| Variations | Ask the Agent for multiple variations at once |
| Limit on variations | Not stated on the page |
| Credit cost | Not stated on the page |
Path 1: several video jobs
Each variation is one POST /v1/videos call with its own prompt. Sume accepts a valid job even when your workspace is already running its limit: the job waits as queued until a processing slot opens, and a full queue returns 429 queue_full (Generation admission).
Send an Idempotency-Key on each submit so a retry returns the original job instead of a second charge. Take the finished video from the job result, or register a callback_url and let the webhook tell you.
- Free plan: 1 job processing, 5 queued
- Pro: 4 processing, 20 queued
- Startup: 8 processing, 40 queued
- Scale: 20 processing, 100 queued
- The dashboard Concurrency tab is the source of truth for your effective limit
Path 2: a Format bulk run
If every variation follows the same recipe, save it as a Format and queue the items. A bulk request is a server-side queue of ordinary Format runs: up to 100 items with a concurrency window, created with POST /v1/formats/{handle}/{slug}/bulk-runs and read back with GET /v1/format-run-queues/{queue_id} (Bulk runs).
Each item is one full Format run with its own receipt, so one failed variation does not take the others down. There is no public cancel for the whole queue; you cancel a child run.
What differs from Flow
Flow's Agent plans and phrases the variations for you. On Sume you write the variation prompts yourself, or let a Format do it from an instruction per item. If you want a model to draft the prompts first, that is a separate step before you submit jobs.
Cost on Sume is per job at the model's catalog rate, reserved on submit, so a batch of variations is the per-clip price times the count. Read the per-model price from GET /v1/videos/models before you queue a large set.
Sources
Related posts
More in Comparisons
- Flow image edits keep the original in History: the Sume edit API
Flow keeps every earlier version in a History panel when you edit an image, with Nano Banana Pro by default. Sume returns a new image URL per edit call.
- Flow custom voices only work with ingredients: what Sume video does
Flow lets you build a custom voice but only for video runs that use ingredients. The Gemini API can't edit voices, and Sume video takes no voice reference.
- Flow Tools vs Sume Formats: a saved creative tool you can call by API
Google Flow Tools lets users build custom creative tools from plain language and share them. A Sume Format is a saved recipe you call over HTTP.
- FLUX 3 Image reference size: 256 px to 16 MP, and Sume URL rules
BFL says each FLUX 3 Image reference is 256x256 px to 16 MP, 1 to 10 images. Sume lists FLUX.2 ids; its reference rules are public HTTPS and a catalog count.
Written by Sume