Together AI lists Seedance 2.5 at $0.115 per video: what it can mean

Together AI's Seedance 2.5 page shows "Price $0.115 / video" without saying how long the video is or what resolution it renders, so the number cannot be compared with a per-second or per-token price until Together says what a video is. The same page also shows a "Launching soon" block asking visitors to be notified when the endpoint goes live, which makes it unclear whether the price is live. On Sume the price is explicit: 4 seconds at 480p is $1.08 and 30 seconds at 1080p is $42.65.

Two readings of $0.115

What the Together page does say

The page lists up to 30 s per generation, up to 30 images, 10 video clips and 10 audio clips as reference capacity, a 99.9% SLA on serverless, and text, image, video and audio inputs. It lists two neighbouring models with per-video prices too, FLUX 3 at $0.17 and MiniMax H3 at $0.1391, so the per-video label is used consistently on that page but the unit is not defined.

How Sume prices the same model

Sume bills Seedance 2.5 at the provider list price per 1000 video tokens times 1.25. Tokens are ceil(width x height x seconds x 24 / 1024). For 4 s at 480p 16:9 (864 x 496) that is 40,176 tokens, and 40.176 x $0.0214 x 1.25 = $1.0747, rounded up to $1.08 per job. For 30 s at 1080p it is 1,458,000 tokens at $0.0234 per 1000, which gives $42.65.

Wan 3.0 on Sume is easier to read: 4 s at 480p is 4 x $0.05 x 1.25 = $0.25.

Normalising any price to cost per second

Divide the price by the seconds it buys. Sume's 30 s Seedance 2.5 clip at 480p is $8.07 over 30 s, which is $0.269 per output second. At 1080p it is $42.65 over 30 s, or $1.42 per output second. A per-video price only reaches that comparison if the vendor tells you the length. Until Together does, any claim that it is cheaper or dearer than Sume is a guess, and this post does not make one.

The Together page also lists Seedance 2.5 as released on July 30, 2026 and describes native audio, 30 s clips and multi-round extension. Sume's own docs state the 4 to 30 second range and the per-token billing, and say nothing about extension, so treat extension as a vendor claim.

Before you budget on a per-video price

• Ask the vendor for duration, resolution and audio settings that the price covers.
• Check whether the endpoint is live; the page asks visitors to be notified when it is.
• Compare on cost per output second, which is the only number that works across per-token, per-second and per-video pricing.
• On Sume, read pricing_skus from GET /v1/videos/models.