A 60 s video as six 10 s shots on two models: $33.54

A 60-second video planned as six 10-second shots, with two hero shots on Seedance 2.5 at 1080p and four supporting shots on Wan 3.0 at 720p, costs $33.54 including the Timeline render (as of 2026-10-08). Sume has no storyboard feature in its docs; the shot list is your own planning step.

The shot list

Write the six shots as a table of start time, purpose, model and resolution. The prices come from the grid, in 9:16.

Totals

Hero: 2 x 1422 = 2844 cents. Support: 4 x 125 = 500 cents. Timeline: ceil(60/60) x 10 = 10 cents. Sum: 3354 cents, $33.54. For comparison, all six shots on Seedance 2.5 at 1080p cost 6 x 1422 + 10 = 8542 cents ($85.42), and all six on Wan 3.0 at 720p cost 6 x 125 + 10 = 760 cents ($7.60).

The mixed plan puts 85% of the spend on a third of the screen time. That is deliberate: viewers judge a video by its opening and its standout moments.

Matching shots across models

Different models will not match each other's look by default. Feed the same reference images to every shot, and fix colour or crop in the Timeline fit option if sizes differ (cover is the default; contain and blur are available).

Timeline's default output is 1080 x 1920, so 9:16 sources fill the frame. Landscape sources would be cropped under cover, so generate in the aspect you will publish.

Variants

Swap the two hero shots to 720p on Seedance 2.5 and the total becomes 2 x $5.78 + 4 x $1.25 + $0.10 = $16.66. Make all four support shots 480p on Wan and it drops by 4 x ($1.25 - $0.63) = $2.48.

Add a third hero shot at 1080p and the total is $33.54 - $1.25 + $14.22 = $46.51. The shot list is the lever: each swap is a line you can price in advance.

Check the number yourself

To confirm the figure behind this post, read the seedance-2.5 entry from GET /v1/video-router/models and check that 10 s and 1080p are inside its duration_seconds and resolutions. The grid price for that cell is 1422 cents ($14.22). It is the provider list price times 1.25, rounded up to the next cent for the job, as of 2026-10-08.

Use an Idempotency-Key on every create call so a retry cannot start a second paid job, then poll the job until it is complete and download the file from the result. Media inputs for Timeline or for references must be hosted files, so import them first.

None of the prices here say anything about picture quality, motion or how well a model follows a prompt. Prices can change when a provider changes its list, which is why every table carries a date. Re-read the catalog before you commit a large batch, and run one test job at the exact setting you plan to use.