Alibaba Wan 3.0 Model Studio request to a Sume /v1/videos body

A Model Studio call to wan3.0-video becomes a Sume call with model: wan-3.0: the media array turns into frame_images and input_references, the parameters object is flattened, and the async header goes away because /v1/videos is always asynchronous. Sume lists one wan-3.0 id, so the standard and wan3.0-video-prime variants do not both appear.

Which Model Studio fields have a Sume home?

Each row pairs an Alibaba field with where it goes in a Sume body (read 2026-10-09).

What do the other differences change?

Four differences change how you write the client.

• Model Studio uses a workspace id and one of six regional hosts. Sume has one base URL, https://api.sume.com.
• Model Studio task ids and video URLs last 24 hours. A Sume job is read at polling_url.
• Pricing is a Sume list times 1.25, reserved at submit; check GET /v1/videos/models for the live pricing_skus.

What does the finished Sume body look like?

This is the body for a 6-second 720p clip with one first frame and a 16:9 frame.

{
  "model": "wan-3.0",
  "prompt": "Image 1 is the opening frame; she lifts the cup and smiles",
  "duration": 6,
  "resolution": "720p",
  "aspect_ratio": "16:9",
  "generate_audio": true,
  "frame_images": [{
    "type": "image_url",
    "image_url": {"url": "https://example.com/frame.png"},
    "frame_type": "first_frame"
  }]
}

The Model Studio fields come from Alibaba's Wan3.0 API reference; the Sume side is in the video generation docs.