Seedance 2.5's 4-second minimum costs $1.07 at 480p 9:16
Seedance 2.5 accepts 4 to 30 seconds, and the shortest 480p 9:16 clip is $1.074709, over the $1.00 default schedule cap. Price points and what to do.

The shortest Seedance 2.5 clip on Sume, 4 seconds at 480p in 9:16, costs $1.074709, which is already over the $1.00 default cap of a scheduled run. Seedance is token-priced, so the total depends on resolution, seconds and aspect ratio rather than a flat per-second rate.
Three price points
Seedance 2.5 accepts 4 to 30 seconds at 480p, 720p and 1080p. The rows below come from the Sume price tool at 9:16; the per-second figure is the total divided by seconds.
| Clip | Seconds | Per second | Total | Under $1.00 |
|---|---|---|---|---|
| 480p | 4 | $0.2687 | $1.0747 | No |
| 720p | 10 | $0.5778 | $5.778 | No |
| 1080p | 30 | $1.4216 | $42.6465 | No |
What to do instead
Use a model with a flat rate for a scheduled run on the default cap, such as Wan 3.0 at 480p ($0.0625 per second, 16 seconds for $1.00), or raise the schedule's cap where you author it. An API caller cannot raise it per run:
curl -sS -X POST "https://api.sume.com/v1/actions/$ACTION_ID/runs" \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: $(uuidgen)" \
-d '{"generation_spend_cap_usd": 5}'Limits and gotchas
The request above sends 5, but the API clamps a number to min(request, schedule cap), so a $1.00 schedule still runs at $1.00. This is by design, so a caller cannot spend past the cap its owner set.
0is a 400, andnullruns without the automation ceiling.- Seedance 2.5 prices move with aspect ratio; rerun the price for 16:9 before you budget.
- The Developer API cannot edit a schedule, so a cap change is made by whoever owns the schedule.
Sources
Related posts
More in Agents
- Six locales, six Agent Completions at $2 each: a $12 worst case
One Agent Completion per locale, each with its own spend cap and Idempotency-Key. Six runs at $2 bound generation to $12, and a retry cannot start a seventh.
- Canceled and skipped Sume agent runs send no webhook: what to poll
A Sume run webhook fires only when a run completes or fails. Canceled and skipped runs send nothing, so your scheduler must read status_url for them.
- A 20,000-character narration fits a $1.00 scheduled cap at $0.95
Sume TTS at $0.0475 per 1,000 characters prices 20,000 characters at $0.95, 5 cents under the $1.00 default cap of a schedule. What 21,000 does.
- Unattended agent: stop or retry on Sume 402, 409, 429, 503?
An unattended Sume agent should stop on 402, fix on 400, retry 429 and 503 with the same idempotency key, and never reuse a key after a 409.
Written by Sume