Is the Seedance 2.5 API live? What Sume can call for 30-second video

ByteDance's Seedance 2.5 post said its API was coming soon via BytePlus ModelArk. On Sume, seedance-2.5 (4-30 s) and wan-3.0 (2-30 s) are in the Video Router.

5 min readSume
All posts

The ByteDance post we read on 2026-10-05 says Seedance 2.5's API is coming soon via BytePlus ModelArk, so check BytePlus for its current status. On Sume you do not have to wait for that: seedance-2.5 (4 to 30 seconds) and wan-3.0 (2 to 30 seconds) are both rows in the Video Router catalog.

Announced versus callable

A model announcement and a callable API are two different things, and the dates matter. Seedance 2.5 launched on 2026-07-31 per ByteDance Seed; Wan 3.0 launched around 2026-08-24 per TechNode; Gemini Omni 1.1 Flash followed on 2026-08-27 per Google. The table lists where each vendor says you can use it and what Sume documents.

30-second-class video models: vendor availability and Sume rows (vendor pages and Sume docs, read 2026-10-05)
ModelVendor saysSume Video Router
Seedance 2.5Rolling out on Jimeng AI and Doubao Pro; API coming soon via BytePlus ModelArkseedance-2.5, 4-30 s, 480p/720p/1080p
Wan 3.0Official website, an exploration site and QwenCloud; closed beta or API, not open weightswan-3.0, 2-30 s, 480p/720p/1080p
Gemini Omni 1.1 FlashAI Studio, Gemini API, Google Flow, Gemini appgemini-omni-flash-1.1, 3-10 s, 360p-4K

Where the vendor facts come from

Sources: ByteDance Seed's Seedance 2.5 post, the Wan 3.0 repository, TechNode and Google's Omni 1.1 Flash post, all read 2026-10-05. We did not find a BytePlus page that confirms the API is live, so we make no claim about it.

Check the catalog, not the launch post

Sume lists the available models at GET /v1/video-router/models, and the docs say the response includes capabilities, because each model can have a different envelope. The catalog is the source of truth for what your key can call. Read it before you build a plan around a model name from a launch post.

curl https://api.sume.com/v1/video-router/models \
  -H "Authorization: Bearer $SUME_API_KEY"

curl https://api.sume.com/v1/video-router/models/wan-3.0 \
  -H "Authorization: Bearer $SUME_API_KEY"

Unknown ids fail

The router rejects ids that are not in the catalog. If a caller wants Sume-owned routing and not a fixed id, it sends model: "sume/auto" instead. Seedance 2.5 has no bitrate_mode in Sume's docs, and neither does Wan 3.0 (the schema rejects it for Wan).

What the two cost

What Sume bills is the provider list times 1.25. Wan 3.0's list is flat by resolution, so a 30 second clip is $1.875, $3.75 or $7.50 on Sume. Seedance 2.5 is priced by video tokens in the repo ($0.0214 per 1,000 tokens at list, $0.0234 at 1080p), so a quote depends on resolution and length; use the catalog price field.

How to choose among the three

Start from the length you need. Over 10 seconds in one take, the candidates are Seedance 2.5 (4 to 30 s) and Wan 3.0 (2 to 30 s). Under 10 seconds with a 4K or 360p tier, Omni Flash 1.1 (3 to 10 s) is the option. Then compare the price in the catalog for the resolution you need.

Run the same prompt on two candidates at the lowest tier before committing. Wan's 2 second 480p minimum is $0.125, which makes it a cheap way to test a prompt, and the lessons carry over when you pick the final model.

Why vendor timing matters

Launch posts describe what a vendor plans, and plans change. Treat a feature as available to you only when it appears in the Sume catalog or the Sume docs, and re-check the catalog when you start a new project.

What to do this week

List the three things your project needs: length, resolution and any reference input. Query the catalog once, keep the response in your repository, and write the model id into configuration rather than code. When a vendor announces a new API, you then change one value and run your proof clips again.

Run proof clips on the cheapest tier of each candidate. A 2 second 480p Wan clip is $0.125, and that is enough to compare prompt adherence before you spend $7.50 on a 1080p render.

A planning rule

A short rule: if a feature appears on a vendor page but not in the Sume docs, plan as though you do not have it. Seedance 2.5's timestamp-level editing, green-screen background replacement and camera perspective change (vendor feature list) are in that group. The Sume fields are in the Video Router docs.

Sources

Related posts

More in Models

All Models posts

Written by Sume