Seedance 2.5 API: Seed blog says soon, BytePlus says live
Two ByteDance pages disagree on Seedance 2.5 API access. Here is what each says, and the seedance-2.5 id that runs on Sume's video router today.

Is the Seedance 2.5 API available? The two ByteDance pages I read today do not agree. The Seed announcement says API access is "coming soon via BytePlus ModelArk", while the BytePlus Seedance product page carries the headline "Dreamina-seedance-2.5 API Now Fully Available to Clients". If you need a call that works from your own code today, Sume's video router lists seedance-2.5.
What each page says
The Seed announcement describes up to 30 seconds per generation with multi-round extension, and references of up to 30 images, 10 video clips and 10 audio clips per pass. It says the model is rolling out on Jimeng AI and Doubao Pro. It lists no resolution tiers and no prices.
The BytePlus product page showed only its headline when I loaded it; the body, its pricing page and its docs pages did not render for me. So I cannot tell you a BytePlus price, region list or rate limit, and this post does not quote any.
| Page | Statement on API access | Details readable |
|---|---|---|
| Seed announcement | API access coming soon via BytePlus ModelArk | Specs yes, prices no |
| BytePlus Seedance page | Headline says API now fully available | Headline only |
| Sume docs | seedance-2.5 listed in the video router | Durations, resolutions, references |
What runs on Sume
Sume's video models docs list seedance-2.5 with 4 to 30 second clips, 480p, 720p and 1080p, native audio, and image, video and audio references. Aspect ratios are 21:9, 16:9, 4:3, 1:1, 3:4 and 9:16. Sume bills the list price times 1.25, rounded up to cents.
Older seedance-2, seedance-2-fast and seedance-2-mini stay routable by explicit id.
A practical rule
When two vendor pages conflict, treat the more conservative one as true until you can make a request. List the model ids your account can see through GET /v1/videos/models and plan around that response, not a headline. The video router docs describe the shape of that list.
Checks before you commit
Because the vendor pages disagree, write down what you need before you choose an access path. Most teams care about four things: whether the model id is callable with a key you already hold, which regions can use it, what the per-token price is, and what the rate limit is. None of those four can be confirmed from the Seed announcement, and I could not read them on the BytePlus page either.
Sume's table above is the opposite situation. Its docs list the id, the duration range, the resolutions and the reference types, so you can write the request today. Pricing is stated as a rate per thousand video tokens in Sume's pricing tables, and the billed amount is list times 1.25 rounded up to cents.
Sources
Related posts
More in Models
- Seedance 2.5 reference-to-video: what Sume accepts per pass
ByteDance lists up to 30 images, 10 videos and 10 audio clips per pass for Seedance 2.5. Here is how that maps to Sume's seedance-2.5 reference types.
- seedream-v4 or bytedance-seed/seedream-4: which Sume id to store
Sume accepts legacy bare ids like seedream-v4 and seedream-4-5-edit, but the catalog lists org/slug ids. Store the canonical id; Python normalizer inside.
- Sora API ended Sept 24: replacements for 15-second clips on Sume
If your Sora code made 15-second clips, Sume has Kling 3, MiniMax H3 and Seedance 2.5 or Wan 3.0 at that length, with prices per clip and one request shape.
- New AI video models in 2026: which ones have a Sume model id
Seedance 2.5, MiniMax H3, Kling 3.0, Wan 3.0, LTX-2.5, Veo 3.1: a table of what a video tracker lists against the ids in Sume's Video Router catalog.
Written by Sume