Estimate a 12 s 9:16 1080p Seedance 2.5 clip before running it: $17.06
A 12-second 9:16 1080p Seedance 2.5 clip is 583,200 video tokens, $17.06 on Sume; here is the arithmetic so you can quote any clip before running it.

A 12-second 9:16 1080p Seedance 2.5 clip is 583,200 video tokens and costs $17.06 on Sume. You can reproduce this before you submit anything, with four numbers: the output size, the seconds, 24 frames a second, and the per-token rate.
ByteDance describes Seedance 2.5 as making 30-second audio-video clips in a single pass (Seed blog, read 2026-10-07), and Sume lists it as seedance-2.5.
The five steps
The estimate follows this order, using the repository rates as of 2026-10-07:
- Pick the output size: 9:16 at 1080p is 1080x1920.
- Tokens = width x height x seconds x 24 / 1024 = 1080 x 1920 x 12 x 24 / 1024 = 583,200.
- Provider list = tokens / 1,000 x $0.0234 at 1080p = $13.65.
- Sume price = list x 1.25 = $17.06.
- The reservation at submit is this amount; the capture on success matches it.
Same clip, other settings
Sume bills the provider list rate multiplied by 1.25 on every video model (Video Router). The figures here come from the price estimators in Sume's repository, run on 2026-10-07, and are rounded to the cent. The live numbers for your workspace are in the catalog response and on the API pricing page.
| Setting | Tokens | Sume price |
|---|---|---|
| 480p 9:16, 12 s | 120,528 | $3.22 |
| 720p 9:16, 12 s | 259,200 | $6.93 |
| 1080p 9:16, 12 s | 583,200 | $17.06 |
Let the API do the check
Do the hand calculation as a sanity check, then ask the platform. The catalog (GET /v1/videos/models) lists the pricing SKUs for each model (Video generation), and from MCP a paid tool accepts dry_run=true to return the estimate without spending (MCP tools and gates).
Sume reserves the estimated amount when it accepts a job, captures it on success, and refunds the reservation if the job fails or is cancelled before capture (Usage, Generation admission). So the balance you need on hand at submit time is the price of everything in flight, not only the final total.
- If your hand figure and the dry run differ by more than a cent, check the resolution and the duration you sent.
- Reference videos change the quote; a reference-video request is priced differently from plain text-to-video.
Check the figures against your own account
After a first job, read the usage row for that job and compare the captured amount with the table; if they differ, trust the ledger. The balance call below only reads your USD balance and starts no job.
curl https://api.sume.com/v1/balance \
-H "Authorization: Bearer $SUME_API_KEY"What these figures leave out
The prices here cover video generation only. Provider list rates can change, so treat a quote from last month as dated and rerun the arithmetic with the current catalog rates.
Sources
Related posts
More in Developers
- Price a mixed image batch first: endpoint pricing in Python
Read cost_usd from each Sume image endpoint and multiply by the count. 200 Grok, 50 Seedream 4.5 and 100 Flux 2 Pro images should total $11.25 before you spend.
- Estimate a Gemini TTS bill from seconds of audio (Python, 25 tok/s)
A 20-line Python estimator for Gemini 3.8 Flash and Flash-Lite TTS audio output cost from seconds, at 25 tokens per second and Google's 2026 and 2027 rates.
- Fade in and out on a Timeline render: output fade seconds 0 to 5
Set output.fade_in_seconds and fade_out_seconds (0 to 5 s, sum within the render length). The music bed has its own fade_out_seconds, up to 10.
- Fast-cut Shorts in Timeline: eight chained fades, then a hard cut
Timeline refuses more than 8 adjacent fades with too_many_chained_transitions. Transitions must be 1 s or less and half the shorter neighbour. How to plan cuts.
Written by Sume