---
title: Video Router
description: Explicit pass-through video generation via the Video Router catalog, including Seedance.
---

New integrations should use [Video generation](/models/videos)
(`POST /v1/videos`) instead — it is the same catalog and the same jobs behind an
OpenRouter-compatible wire. Video Router stays available and unchanged.

Video Router is Sume's **explicit model catalog** for video generation. You pick
a catalog `model` id from `GET /v1/video-router/models` (for example Seedance);
Sume bills list × 1.10 and returns the usual async job envelope.

For most partners, prefer **[Video 1.0](/models/video)** with `routing_preset`
instead — Sume chooses the model. Use Video Router when you need a specific
catalog id.

Primary invoke URL:

```text
POST /v1/video-router/generate
```

Catalog:

```text
GET /v1/video-router/models
GET /v1/video-router/models/{model_id}
```

## When to use

| Goal | Approach |
|---|---|
| Let Sume pick | Prefer [Video 1.0](/models/video) + `routing_preset` |
| Pin a catalog model (e.g. Seedance) | Video Router + `model` from the catalog |

## Create a Video Router job

```bash
curl -X POST https://api.sume.com/v1/video-router/generate \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: video-router-001" \
  -d '{
    "model": "seedance-2.5",
    "prompt": "A vertical UGC-style product clip on a desk, natural light",
    "resolution": "720p",
    "duration": 12,
    "aspect_ratio": "9:16",
    "mode": "async"
  }'
```

Limits are per model — `seedance-2.5` accepts 4–30s at 480p/720p/1080p,
`wan-3.0` accepts 2–30s, and `minimax-h3` accepts 5–15s at native 480p/768p
(768p is first-class, not 720p). Every other catalog model is capped at 15s.
`seedance-2` also offers 1080p. Read `capabilities` from
`GET /v1/video-router/models` rather than assuming one envelope.

See the [API reference](/api/reference) OpenAPI paths under **Video Router** for
the full request schema and catalog fields.