Flow charges 7 to 15 credits for Omni Flash; Sume bills dollars

In Google Flow a Gemini Omni Flash clip at 720p costs 7 to 15 credits depending on its length, and a 360p clip costs 4 to 7. On Sume the same model, gemini-omni-flash-1.1, is billed in dollars per output second: 720p is $0.125 a second, so a 10-second clip is $1.25 and a 3-second clip is $0.375.

The Flow numbers come from Google's Manage your Google Flow credits page, and the model limits from the Gemini Omni Flash API page, both read on 2026-10-02. The Sume side comes from the Video Router docs. The two systems are not directly convertible, and this post says where the comparison breaks.

What does Gemini Omni Flash cost in Flow credits?

Google's credits page lists Omni Flash at 720p as 7 to 15 credits depending on clip length, and at 360p as 4 to 7 credits. It does not print a per-length table on the page I read, so the in-between lengths are not quoted here. Two other lines matter for planning: 1080p upscaling is free for Google AI Plus, Pro and Ultra subscribers, and 4K upscaling is 50 credits and Ultra only.

The Gemini API side is different. Google's pricing page bills Omni Flash by tokens ($17.50 per 1M video output tokens) and states an approximate $0.10 per second at 720p. That is the number to hold next to Sume's rate, since both are per second of output video, not per credit.

How does Sume price the same model?

Sume bills provider list price times 1.25 per output second, by resolution. The Video Router docs state the 1.25 multiplier and the 3 to 10 second range at 360p, 720p, 1080p and 4K in 16:9 or 9:16, with native synced audio always on. The per-second rates by resolution are in the catalog's pricing_skus field, so read them from GET /v1/video-router/models instead of trusting a blog table that may age.

The practical difference is shape. A Flow credit is a unit inside a subscription, so the price of a clip depends on your plan. A Sume job is a dollar amount reserved from a workspace balance before work starts, and a request that cannot be reserved fails with 402 insufficient_credits per the generation admission docs.

When is Flow the better fit?

If you already pay for a Google AI plan and make clips by hand, Flow is simpler: Google bundles monthly credits (200 for Plus, 1,000 for Pro, 10,000 and 25,000 for the two Ultra tiers) and the interface handles editing and upscaling. Flow also has its own agent and tooling that Sume does not copy.

If you need Omni Flash inside a pipeline, such as a nightly batch of product clips or a webhook-driven app, a per-second price you can compute before submitting is easier to budget than a credit pool. Sume also takes one request shape for text, image and reference modes.

How do I submit one Omni Flash clip on Sume?

Send POST /v1/video-router/generate with an idempotency key. The request below asks for 8 seconds at 720p, which reserves $1.00 at the rate above, and mode: async returns a job to poll instead of holding the connection.

curl -X POST https://api.sume.com/v1/video-router/generate \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: omni-clip-001" \
  -d '{
    "model": "gemini-omni-flash-1.1",
    "prompt": "A ceramic mug on a wooden desk, steam rising, soft morning light",
    "duration": 8,
    "resolution": "720p",
    "aspect_ratio": "16:9",
    "mode": "async"
  }'

Does the model behave the same in both places?

Both routes call Gemini Omni Flash, so the prompt rules carry over. Google's Omni page says English is fully supported and other languages were not evaluated, that temperature, top_p, stop sequences and negative prompts are unsupported, and that all output carries a SynthID watermark. Those are properties of the model, not of Flow or Sume, and they apply to either path.

What differs is the wrapper. Flow adds an editor, an agent and a credit pool. Sume adds a job record with an id, status and result URL, an idempotency key on submit, and a single balance shared with every other model in the catalog. Pick the wrapper that matches how the clip will be used, then compare costs inside it.

What does this comparison leave out?

Flow credits are not dollars, and I did not fetch Google's plan prices, so there is no dollars-per-credit conversion here. Free-tier access to Omni Flash in Flow is not confirmed on the credits page either. Treat the table as Sume dollars beside Google's published credit ranges and API rate, not as a verdict on which is cheaper for your plan.