Cent rounding on 100 clips: Omni 1080p at list x 1.25 on Sume

Sume's Video Router bills each model at provider list price times 1.25, and the catalog formula rounds up to the cent. That rounding is invisible on one clip and visible on a batch: a ten-second Gemini Omni Flash 1.1 clip at 1080p has an exact price of $1.875, which bills as $1.88, so 100 of them cost $188.00 rather than $187.50. If the ceiling applies once per job, as the catalog formula reads, budget the rounded figure, not the exact one.

The arithmetic

Omni 1080p lists at $0.15 per second in Sume's Video Router notes. Times 1.25, that is $0.1875 per second. The rounding is applied to the clip total, so the clip length decides how much it adds. Runway's pricing guide lists gemini_omni_flash at 10 credits per second with credits at $0.01, which is a flat $0.10 per second on its page, a useful reminder to compare the unit and the resolution before comparing totals.

What to do with the cents

Rounding is not a reason to change a plan. It is a reason to stop reconciling against a spreadsheet that multiplies seconds by a rate. The poll response for /v1/videos carries usage.cost, the Sume billable amount for that job, so sum those instead. A gap under 0.3 percent between your estimate and the ledger on a 10-second clip is rounding, not a bug.

Clip length shifts the effect. Eight seconds at this rate lands on an exact cent, so there is no rounding at all, while 3, 5 and 10 seconds each round up. When you pick a standard length for a production batch, remember that a length that divides evenly into cents is slightly cheaper in aggregate than its neighbors.

• Estimate with the rate times seconds, then add one cent per clip as an upper bound.
• Reconcile from usage.cost on each completed job, never from the estimate.
• Reserve is not the same as capture: the reserve at submit is list times 1.25, so a wallet check can look slightly stricter than the final bill.

Check the live rate before relying on this

Rates change, and the numbers above come from the rows documented on read date. Call GET /v1/videos/models and read pricing_skus for the model you use. The per-second list price in the Video Router notes carries the date it was read from the provider.