Why a 3-second Gemini Omni clip bills 12 cents, not 11, on Sume

If you multiply by hand, a 3-second Gemini Omni Flash 1.1 clip at 360p looks like $0.09 of provider cost times 1.25, or $0.1125. The Sume invoice line says $0.12. That is not an error: the Video Router docs bill list times 1.25, and Sume's pricing code rounds each job's billable amount up to the next cent.

The four resolutions at the minimum length

Omni Flash 1.1 on Sume runs 3 to 10 seconds. The list rates are the fal prices of $0.03, $0.10, $0.15 and $0.30 per second at 360p, 720p, 1080p and 4K (fal page read 2026-10-05). The table shows the shortest allowed clip and an 8-second clip, which is Sume's default length for sume/auto.

Why it matters for batches

Rounding is per job, not per second. A hundred 3-second 720p clips are a hundred $0.38 lines, which is $38.00, not the $37.50 you get from 100 x 3 x $0.125. The gap is small, but a finance export that reconciles to the cent will show it.

• Budget with the rounded per-clip figure, not per-second x seconds.
• Read usage.cost on each completed job; it is the Sume billable amount.
• One 8-second clip at 720p is exactly $1.00 because 8 x $0.125 needs no rounding.

Request

The call is the same one you use for any catalog model. Send model: "gemini-omni-flash-1.1", a duration of 3, and resolution of 360p. The default resolution is 720p.

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-3s-360p-001" \
  -d '{
    "model": "gemini-omni-flash-1.1",
    "prompt": "A paper boat crossing a puddle, rain sounds",
    "duration": 3,
    "resolution": "360p",
    "aspect_ratio": "16:9",
    "mode": "async"
  }'