Wan 3.0 at 480p plus video upscale, 20 s: $1.43 vs $5.00 native 1080p

Generate 20 s of Wan 3.0 at 480p (20 s × $0.0625 = $1.25) and add Sume's video upscale at $0.009 per video second (20 × $0.009 = $0.18) for $1.43. Native 1080p for the same 20 s is 20 s × $0.25 = $5.00. Whether the upscale suits you depends on the output size it returns, which this page does not state.

Prices on this page are Sume list prices as of 2026-10-08: the provider list price times 1.25, computed from Sume's pricing package and billed per output second, linear in duration inside each model's valid range. The model ids, ranges and input types come from the Video generation docs and the Video Router docs; the per-second numbers can be cross-checked in the public catalog. The video upscale price is from the same catalog (read 2026-10-08).

The comparison

The saving is $3.57 for 20 s. The upscale input is limited to 30 s, so the route works for any Wan 3.0 clip up to the 30 s maximum.

What an upscale cannot do

An upscale enlarges the pixels it has. It does not add the detail a native 1080p render would draw from your prompt, so faces, text and fine textures are the places to compare. Render one short sample both ways, put them side by side at the delivery size, and decide on that, not on price.

Because the price is linear, a 5 s test is a quarter of the cost: $0.3575 for 480p plus upscale against $1.25 native.

Scaling this plan up or down

As a yardstick, the plan above is built on Wan 3.0 at 480p, $0.0625 per second. Each extra 5 seconds adds $0.3125, a further $10 of budget buys 160 more whole seconds, and the largest single job the model accepts (30 s) holds $1.875 at submit. The shortest one (2 s) holds $0.125.

Those three numbers are enough to rescale the plan without a new table. If the plan doubles, double the totals; if a clip is shortened, subtract the seconds multiplied by the rate; and if the tier changes, swap the rate for the one in the tables above.

• Per second: $0.0625
• Per 5 s: $0.3125
• Per 10 s: $0.625
• Per 30 s or the model maximum (30 s): $1.875

Check the model's fields first

After the first job completes, read usage.cost on the poll response and compare it with the figure in this post. They should agree, because both are the provider list price times 1.25. If your number differs, the usual cause is a different tier or duration than you planned, not a price change; the public catalog at https://api.sume.com/v1/catalog shows the current rates and needs no key.

Submitting

Submit through POST /v1/videos with model, prompt, duration in whole seconds and resolution; read GET /v1/videos/models first, because supported_durations and supported_resolutions differ per model. Sume reserves the price at submit and usage.cost on the poll response is the billable amount, so the figures here are what leaves the balance.