Which video models accept 30 seconds on Sume: read the catalog first

On Sume's Video Router, four models list a duration of up to 30 seconds: seedance-2.5 (4 to 30 s), wan-3.0 (2 to 30 s), h3-max-recast (5 to 30 s, a recast of a source video) and higgsfield-genjutsu (4 to 30 s, Motion Transfer, in the catalog only when its provider is configured). Every other catalog model has a limit of 15 seconds or less. Read capabilities from GET /v1/video-router/models before you plan, because each model can have a different envelope.

Durations in the Video Router docs

The vendors are moving the same way. ByteDance says Seedance 2.5 generates up to 30 seconds per generation (read 2026-10-05), and the Wan 3.0 README lists native 30-second generation (read 2026-10-05). On Sume the numbers come from the Router page, and they are the ones your request is checked against.

Preflight in one call

A duration outside the model's range is a request error, and the docs say the catalog is where you read the limits. Make the catalog read the first step of any 30-second plan:

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

What the numbers do not tell you

A model that accepts 30 seconds does not mean 30 seconds is the right clip. The duration field is the output length, and the clip's price scales with output seconds at the catalog rate. The docs give no latency promise, so size your client deadline from your own measurements and not from a vendor's blog.

sume/auto through POST /v1/videos is the other route. Its create controls default to 720p and 8 seconds and cover 3 to 10 second clips at 16:9 or 9:16, so it is not the way to a 30-second render. Pin a catalog model id when you need the longer clip, and expect a different look from the same prompt on a different model.

Choosing within the 30-second group

Several models list 30 seconds, but they do not list the same minimum. Seedance 2.5 runs 4 to 30 seconds, Wan 3.0 runs 2 to 30, h3-max-recast runs 5 to 30, and higgsfield-genjutsu runs 4 to 30 only when its provider is configured. If you need a short clip and a long one from the same code path, the lower bound matters as much as the 30.

Read the model's own entry through GET /v1/video-router/models/<id> and take duration from there, so a catalog change does not break a request that you hardcoded. The sume/auto router covers 3 to 10 second clips and defaults to 720p at 8 seconds, so it is not the route for a 30 second render.

The vendor pages describe what the models do outside Sume, for example Seedance 2.5 and Wan 3.0 both advertise native 30 second generation (read 2026-10-05). What Sume accepts is what the catalog lists.

• Read the catalog for the live range.
• Do not send 30 to MiniMax H3; it stops at 15.
• Do not use sume/auto for 30 seconds.