POST /v1/videos vs POST /v1/video-router/generate on Sume

Sume's docs recommend POST /v1/videos for new integrations; Video Router stays available and unchanged. Same catalog, same jobs, different request shape.

5 min readSume
All posts

Use POST /v1/videos for new integrations. Sume's Video Router docs say so directly: Video generation has the same catalog and the same jobs behind an OpenRouter-compatible wire, and Video Router 'stays available and does not change'. If you already call POST /v1/video-router/generate, nothing forces you to move.

Side by side

Facts below come from the two Sume docs pages.

Video endpoint comparison, as of 2026-10-09 (Sume docs)
QuestionPOST /v1/videosPOST /v1/video-router/generate
RecommendationNew integrationsStays available, unchanged
Wire formatOpenRouter-compatibleSume's explicit model catalog
Model catalogGET /v1/videos/modelsGET /v1/video-router/models
Let Sume pick the modelmodel: sume/autoVideo Router Auto is reached through /v1/videos
Pin a modelCatalog model id, such as seedance-2.5Catalog model id from the router catalog
BillingProvider list x 1.25Provider list x 1.25

Auto defaults and limits

With sume/auto, the Auto create controls default to 720p and 8 seconds, with 3 to 10 second clips in 16:9 or 9:16. Pinned models have their own ranges: seedance-2.5 accepts 4 to 30 seconds and wan-3.0 accepts 2 to 30. Check the model before you submit, because limits differ per model.

The Video Router docs example sends an Idempotency-Key header with the job request. If you retry a submit, send the same key so you do not pay for two jobs.

What about Video 1.0?

The docs say Sume will retire Video 1.0 soon, and until then it is a compatibility alias for the same Auto pipe. If your code posts to a Video 1.0 route, plan to move it to /v1/videos with model sume/auto. See the Video generation docs and the Video Router docs.

Sources

Related posts

More in Comparisons

All Comparisons posts

Written by Sume