Video Router price band: 2 cents to $42.86 and a 50 cent estimate
The Sume Video Router row shows 50 cents estimated, 2 cents minimum and $42.86 maximum. See why the spread is wide and how to narrow it before you submit.
Why does the Video Router list 2 cents to $42.86?
The Video Router row in the Sume catalog is a band across every model the router can run, so it is wide on purpose. The estimate is 50 cents, the minimum is 2 cents and the maximum is $42.86.
The estimate comes from sume/auto with MiniMax H3 Max defaults at 768p for 5 seconds. Every model on the router bills list price times 1.25, which is why the numbers are not round.
What does each end of the band represent?
The Video Router docs describe the router. This table maps the catalog figures.
| Band | USD | Basis |
|---|---|---|
| Minimum | $0.02 | The cheapest request the endpoint accepts |
| Estimate | $0.50 | sume/auto, H3 Max defaults, 768p, 5 s |
| Maximum | $42.86 | The most one call can reserve |
How do I see which model a request will use?
Call GET /v1/video-router/models to list the models and their capabilities. When you set model yourself, the price follows that model's rate. When you send sume/auto, the router chooses, so the final figure depends on its choice and on resolution and length.
Sume does not publish a single flat per-second price for Auto, because it is a router. If you need a stable number for a budget, pin a model and read its rate.
Is Video 1.0 the same band?
No. Video 1.0 is a retiring alias of Auto and its catalog row shows 57 cents minimum, 232 cents estimated and 1,742 cents maximum. See the Video 1.0 band for that breakdown. The two rows describe different default requests, so do not compare their estimates as if they priced the same clip.
What should I reserve in the wallet?
For a single clip, the estimate is a fair guide. For a batch, multiply your per-clip price by the number of jobs in flight, since each job reserves at submit and settles on completion. A $42.86 maximum is a ceiling for one call and is rarely the right figure for planning.
What does the band mean for a batch?
Take 20 clips at the 50-cent estimate: $10.00. The same 20 clips at the $42.86 maximum would be $857.20, which no normal run reaches. The gap shows why you should treat the estimate as a default-request price and measure a real job before committing a budget.
A practical routine is to submit one clip, read its debited amount with GET /v1/usage?job_id=, and multiply. The summary's debited figure is the number to quote, and you should not add up the rows yourself.
If the figure surprises you, pin a model and re-run, because Auto's pick is the main source of variance.
Sources
Related posts
More in Pricing
- Video-to-video AI cost per clip: Recast and Genjutsu
Video-to-video on Sume costs $0.375 to $0.85 per second: a 10-second Recast clip at 768p is $3.75 and a 10-second Genjutsu clip at 720p is $8.51.
- Vidu Q3 turbo vs pro API price per second: 540p, 720p, 1080p
Vidu lists Q3-turbo from $0.035 and Q3-pro from $0.045 per second, half price off-peak. The per-second table, a 10-second cost, and what Sume offers instead.
- Hosted Wan 3.0 per clip vs running Wan 2.2 on a rented GPU
Sume's wan-3.0 bills $0.0625, $0.125 or $0.25 per second at 480p, 720p, 1080p. Here is the break-even arithmetic against your own GPU hourly rate.
- WaveSpeed starting price: lowest resolution, and a 10 s clip cost
WaveSpeed's page says starting prices are list prices at the lowest resolution or quality. At those rates a 10-second clip runs $0.30 to $1.80. Table inside.
Written by Sume