Vidu Q4 list vs Sume's list x 1.25: Omni 4K is $0.30 before margin
Vidu Q4 4K is $0.39/s at vendor list. Sume bills list x 1.25, so Omni 4K at $0.375 implies a $0.30 provider list; the table compares list to list.

The short answer
Vidu's $0.39 per second at 4K is the vendor's own rate. Sume's $0.375 per second for Gemini Omni Flash 1.1 at 4K already includes Sume's margin, which the Video Router docs state as the provider list price times 1.25. Divide by 1.25 and the implied provider list is $0.30. So on a list-to-list basis Vidu's 4K is 30% above Omni's, while on a price-you-pay basis it is only 4% above. Sume does not list Vidu, so this is a comparison of rates, not a purchase option.
Implied provider list for Sume rows
The middle column is the Sume price divided by 1.25. It is derived, not published by the provider on Sume's pages, so treat it as an implied figure.
| Row | Implied provider list $/s | Sume price $/s |
|---|---|---|
| gemini-omni-flash-1.1, 720p | $0.10 | $0.125 |
| gemini-omni-flash-1.1, 1080p | $0.15 | $0.1875 |
| gemini-omni-flash-1.1, 4K | $0.30 | $0.375 |
| wan-3.0, 720p | $0.10 | $0.125 |
| wan-3.0, 1080p | $0.20 | $0.25 |
Why the distinction matters
Buyers often compare a vendor's list price with an aggregator's price and conclude that the aggregator is expensive. That comparison is fair only if the aggregator gives you something for the margin. On Sume the margin buys one account, one wallet, one API shape and one job model across many providers. If you use only one vendor and do not need those, the vendor's own platform may be cheaper. If you test several vendors in a month, the saving in integration time is real.
The Vidu figures also carry conditions: the discount applies to image-to-video and reference-to-video until November 30, and the release names only two price points.
A rule for quotes
Quote clients from the price you pay, not the list. For a 10-second 4K clip that is $3.75 on Omni and $3.90 on Vidu at list. For a team that runs through Sume, the Sume figure is what leaves the wallet; check it in the catalog at the time you quote, because catalog rates can change. If you invoice per clip, store the price shown in the poll response usage.cost alongside the job id, so the figure you bill is the figure that was charged. The Video Router docs state the pricing rule for each model.
Checking a number yourself
Open the public catalog at api.sume.com/v1/catalog, find the row, and divide by 1.25. For Wan 3.0 at 1080p the Sume price is $0.25, so the implied list is $0.20. For Omni at 360p it is $0.0375 / 1.25 = $0.03. These checks need no account. If the catalog row changes, the division still holds, since the docs describe the multiplier as the house margin for each model rather than for one. Repeat the check whenever you update a budget, since the rows move independently.
Sources
Related posts
More in Pricing
- Vidu Q4 Preview: $0.014 or $0.045 a second? Two releases disagree
One Vidu Q4 Preview release says launch pricing starts at $0.014 a second; another says $0.045 at 540p up to $0.39 at 4K. Compare with Sume's per-second rates.
- Vidu Q4 after Nov 30: +42.9% per second, and what stays flat on Sume
The Vidu Q4 image and reference-to-video discount ends Nov 30, raising rates 42.9%. Here is the 1,000-second bill before and after, next to flat Sume rates.
- Voice API cost gap up to 213x: what drives it, how to price yours
Krisp's newsletter reports a voice API cost gap of up to 213x across OpenAI, Gemini and Qwen. Why list TTS prices differ far less, and how to normalise yours.
- Voiceover cost for a 60-second video: about $0.043 on Sume TTS
A 60-second voiceover is roughly 900 characters, which bills about $0.043 on Sume TTS. The cost at 600 to 1,200 characters, and how to measure your own script.
Written by Sume