200 product ads of 10 seconds on Seedance 2.5: $1155.60

200 product ads of 10 seconds each cost $1155.60 on Sume with Seedance 2.5 at 720p and 9:16. One ad is $5.7780.

Seedance 2.5 accepts 4 to 30 seconds per request (read 2026-10-06 in the video generation docs), so every ad is a single job.

How does resolution change the bill?

Seedance 2.5 is priced by video tokens, so the price rises with pixel count.

What does one request look like?

One POST /v1/videos per ad.

curl -X POST "https://api.sume.com/v1/videos" \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: clip-seedance-2.5-10s-001" \
  -d '{
    "model": "seedance-2.5",
    "prompt": "A product on a desk, slow push-in, natural light",
    "duration": 10,
    "resolution": "720p",
    "aspect_ratio": "9:16"
  }'

How do I keep the run safe?

Prices are read from the rate card on 2026-10-06; confirm in GET /v1/catalog.

• Use a distinct Idempotency-Key per ad.
• Run a single ad first.
• Stop the batch on a 402 and top up before resuming.