Wan 3.0 on Runway, or the wan-3.0 id as an API job on Sume
Runway's changelog lists Wan 3.0 in tool mode and workflows on paid plans. On Sume, wan-3.0 is a model id you call from code and poll as a job.

Runway added Wan 3.0 on Aug 24, 2026 as an option in tool mode and in workflows, at 480p, 720p or 1080p, on paid plans. If you want to call the same model from your own code, Sume exposes it as the catalog id wan-3.0: you send a request and read back a job.
The Runway facts are from its changelog, read 2026-09-30. The Sume facts are from the Video generation and Video Router docs and the catalog in code.
What does Runway say about Wan 3.0?
One changelog line: Wan 3.0 is available in tool mode and workflows at 480p, 720p, or 1080p, for paid plans. The line says nothing about an API, clip length or per-second price, so this post does not state any for Runway.
How does wan-3.0 on Sume compare field by field?
Only the Runway cells that its changelog states are filled in.
| Item | Runway changelog | Sume `wan-3.0` |
|---|---|---|
| How you use it | Tool mode and workflows | Request by model id, then read the job |
| Resolutions | 480p, 720p, 1080p | 480p, 720p, 1080p |
| Clip length | Not stated | 2 to 30 seconds |
| Aspect ratios | Not stated | auto, adaptive, 16:9, 4:3, 1:1, 3:4, 9:16 |
| Availability | Paid plans | Listed in GET /v1/video-router/models |
How do I call wan-3.0 from code?
Post to /v1/video-router/generate with model: "wan-3.0", a prompt and a resolution. It needs an Idempotency-Key, and with mode: "async" you get a job to read later, as in the Video Router docs. Check capabilities from GET /v1/video-router/models before assuming a limit. For longer worked examples see Wan 3.0 video API.
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: wan-3-demo-001" \
-d '{
"model": "wan-3.0",
"prompt": "A paper boat drifting down a rain gutter, close-up",
"resolution": "720p",
"duration": 5,
"mode": "async"
}'What does a Wan 3.0 clip cost on Sume?
Sume bills the provider list price times 1.25 per output second. Computed from Sume's pricing code for a 5-second clip:
480p: $0.32, 720p: $0.63, 1080p: $1.25. The per-second breakdown is in Wan 3.0 pricing.
Which one should I use?
Use Runway's tool mode or workflows if you work inside Runway's editor. Use the wan-3.0 id if the clip must come out of a script, a queue or an agent, where you store the job id and fetch the result later.
Sources
Related posts
- Wan 3.0 API: 2–30 second AI video with audio, frames, and references
- Wan 3.0 pricing: what a clip costs per second at 480p, 720p and 1080p
- Wan 3.0 1080p: how to request full HD from the API
- Wan 3.0 open source: weights on Hugging Face or API only?
- Runway Media Router and sume/auto: what Sume's router does
More in Models
- An OpenRouter-compatible video API: sume/auto or a pinned model
Sume's POST /v1/videos follows OpenRouter's video generation API field for field. Let sume/auto pick the model, or pin a catalog id like seedance-2.5.
- Image generation API with reference images: POST /v1/images
Send a prompt plus public HTTPS reference images to Sume's POST /v1/images. Pin a catalog model or send sume/auto; the catalog lists each model's limits.
- Video 1.0 and Image 1.0 are retiring soon: move to sume/auto
Sume Video 1.0 and Image 1.0 are retiring soon and already run as aliases for the Auto path. New integrations call /v1/videos or /v1/images with sume/auto.
- Music generation API: the Sume Music Router with Lyria 3.5
Sume's Music Router turns a text prompt into a track via POST /v1/music-router/generate. sume/music-auto picks the engine, Lyria 3.5 today.
Written by Sume