Category: provider
Model Studio Wan Video
Validation
mkdir -p output/aliyun-wan-video
python -m py_compile skills/ai/video/aliyun-wan-video/scripts/generate_video.py && echo "py_compile_ok" > output/aliyun-wan-video/validate.txt
Pass criteria: command exits 0 and output/aliyun-wan-video/validate.txt is generated.
Output And Evidence
- Save task IDs, polling responses, and final video URLs to
output/aliyun-wan-video/.
- Keep one end-to-end run log for troubleshooting.
Provide consistent video generation behavior for the video-agent pipeline by standardizing video.generate inputs/outputs and using DashScope SDK (Python) with the exact model name.
Critical model names
Use one of these exact model strings:
wan2.6-t2v
wan2.6-t2v-us
wan2.2-t2v-plus
wan2.2-t2v-flash
wan2.6-i2v-flash
wan2.6-i2v
wan2.6-i2v-us
wanx2.1-t2v-turbo
Prerequisites
- Install SDK (recommended in a venv to avoid PEP 668 limits):
python3 -m venv .venv
. .venv/bin/activate
python -m pip install dashscope
- Set
DASHSCOPE_API_KEY in your environment, or add dashscope_api_key to ~/.alibabacloud/credentials (env takes precedence).
Normalized interface (video.generate)
Request
prompt (string, required)
negative_prompt (string, optional)
duration (number, required) seconds
fps (number, required)
size (string, required) e.g. 1280*720
seed (int, optional)
reference_image (string | bytes, optional for t2v, required for i2v family models)
motion_strength (number, optional)
Response
video_url (string)
duration (number)
fps (number)
seed (int)
Quick start (Python + DashScope SDK)
Video generation is usually asynchronous. Expect a task ID and poll until completion.
Note: Wan i2v models require an input image; pure t2v models such as wan2.6-t2v can omit reference_image.
import os
from dashscope import VideoSynthesis
# Prefer env var for auth: export DASHSCOPE_API_KEY=...
# Or use ~/.alibabacloud/credentials with dashscope_api_key under [default].
def generate_video(req: dict) -> dict:
payload = {
"model": req.get("model", "wan2.6-i2v-flash"),
"prompt": req["prompt"],
"negative_prompt": req.get("negative_prompt"),
"duration": req.get("duration", 4),
"fps": req.get("fps", 24),
"size": req.get("size", "1280*720"),
"seed": req.get("seed"),
"motion_strength": req.get("motion_strength"),
"api_key": os.getenv("DASHSCOPE_API_KEY"),
}
if req.get("reference_image"):
# DashScope expects img_url for i2v models; local files are auto-uploaded.
payload["img_url"] = req["reference_image"]
response = VideoSynthesis.call(**payload)
# Some SDK versions require polling for the final result.
# If a task_id is returned, poll until status is SUCCEEDED.
result = response.output.get("results", [None])[0]
return {
"video_url": None if not result else result.get("url"),
"duration": response.output.get("duration"),
"fps": response.output.get("fps"),
"seed": response.output.get("seed"),
}
Async handling (polling)
import os
from dashscope import VideoSynthesis
task = VideoSynthesis.async_call(
model=req.get("model", "wan2.6-i2v-flash"),
prompt=req["prompt"],
img_url=req["reference_image"],
duration=req.get("duration", 4),
fps=req.get("fps", 24),
size=req.get("size", "1280*720"),
api_key=os.getenv("DASHSCOPE_API_KEY"),
)
final = VideoSynthesis.wait(task)
video_url = final.output.get("video_url")
Operational guidance
- Video generation can take minutes; expose progress and allow cancel/retry.
- Cache by
(prompt, negative_prompt, duration, fps, size, seed, reference_image hash, motion_strength).
- Store video assets in object storage and persist only URLs in metadata.
reference_image can be a URL or local path; the SDK auto-uploads local files.
- If you get
Field required: input.img_url, the reference image is missing or not mapped.
wan2.6-t2v and wan2.6-t2v-us add multi-shot narrative support and optional audio input according to the official docs.
Size notes
- Use
WxH format (e.g. 1280*720).
- Prefer common sizes; unsupported sizes can return 400.
Output location
- Default output:
output/aliyun-wan-video/videos/
- Override base dir with
OUTPUT_DIR.
Anti-patterns
- Do not invent model names or aliases; use official Wan i2v model IDs only.
- Do not block the UI without progress updates.
- Do not retry blindly on 4xx; handle validation failures explicitly.
Workflow
- Confirm user intent, region, identifiers, and whether the operation is read-only or mutating.
- Run one minimal read-only query first to verify connectivity and permissions.
- Execute the target operation with explicit parameters and bounded scope.
- Verify results and save output/evidence files.
References
1---2name: aliyun-wan-video3description: Use when generating videos with Model Studio DashScope SDK using Wan video generation models (wan2.6-t2v, wan2.6-i2v-flash, wan2.6-i2v and regional variants). Use when implementing or documenting video.generate requests/responses, mapping prompt/negative_prompt/duration/fps/size/seed/reference_image/motion_strength, or integrating video generation into the video-agent pipeline.4---5
6Category: provider
7
8# Model Studio Wan Video
9
10## Validation
11
12```bash
13mkdir -p output/aliyun-wan-video
14python -m py_compile skills/ai/video/aliyun-wan-video/scripts/generate_video.py && echo "py_compile_ok" > output/aliyun-wan-video/validate.txt
15```
16
17Pass criteria: command exits 0 and `output/aliyun-wan-video/validate.txt` is generated.
18
19## Output And Evidence
20
21- Save task IDs, polling responses, and final video URLs to `output/aliyun-wan-video/`.
22- Keep one end-to-end run log for troubleshooting.
23
24Provide consistent video generation behavior for the video-agent pipeline by standardizing `video.generate` inputs/outputs and using DashScope SDK (Python) with the exact model name.
25
26## Critical model names
27
28Use one of these exact model strings:
29- `wan2.6-t2v`
30- `wan2.6-t2v-us`
31- `wan2.2-t2v-plus`
32- `wan2.2-t2v-flash`
33- `wan2.6-i2v-flash`
34- `wan2.6-i2v`
35- `wan2.6-i2v-us`
36- `wanx2.1-t2v-turbo`
37
38## Prerequisites
39
40- Install SDK (recommended in a venv to avoid PEP 668 limits):
41
42```bash
43python3 -m venv .venv
44. .venv/bin/activate
45python -m pip install dashscope
46```
47- Set `DASHSCOPE_API_KEY` in your environment, or add `dashscope_api_key` to `~/.alibabacloud/credentials` (env takes precedence).
48
49## Normalized interface (video.generate)
50
51### Request
52- `prompt` (string, required)
53- `negative_prompt` (string, optional)
54- `duration` (number, required) seconds
55- `fps` (number, required)
56- `size` (string, required) e.g. `1280*720`
57- `seed` (int, optional)
58- `reference_image` (string | bytes, optional for t2v, required for i2v family models)
59- `motion_strength` (number, optional)
60
61### Response
62- `video_url` (string)
63- `duration` (number)
64- `fps` (number)
65- `seed` (int)
66
67## Quick start (Python + DashScope SDK)
68
69Video generation is usually asynchronous. Expect a task ID and poll until completion.
70Note: Wan i2v models require an input image; pure t2v models such as `wan2.6-t2v` can omit `reference_image`.
71
72```python
73import os
74from dashscope import VideoSynthesis
75
76# Prefer env var for auth: export DASHSCOPE_API_KEY=...
77# Or use ~/.alibabacloud/credentials with dashscope_api_key under [default].
78
79def generate_video(req: dict) -> dict:
80 payload = {
81 "model": req.get("model", "wan2.6-i2v-flash"),
82 "prompt": req["prompt"],
83 "negative_prompt": req.get("negative_prompt"),
84 "duration": req.get("duration", 4),
85 "fps": req.get("fps", 24),
86 "size": req.get("size", "1280*720"),
87 "seed": req.get("seed"),
88 "motion_strength": req.get("motion_strength"),
89 "api_key": os.getenv("DASHSCOPE_API_KEY"),
90 }
91
92 if req.get("reference_image"):
93 # DashScope expects img_url for i2v models; local files are auto-uploaded.
94 payload["img_url"] = req["reference_image"]
95
96 response = VideoSynthesis.call(**payload)
97
98 # Some SDK versions require polling for the final result.
99 # If a task_id is returned, poll until status is SUCCEEDED.
100 result = response.output.get("results", [None])[0]
101
102 return {
103 "video_url": None if not result else result.get("url"),
104 "duration": response.output.get("duration"),
105 "fps": response.output.get("fps"),
106 "seed": response.output.get("seed"),
107 }
108```
109
110## Async handling (polling)
111
112```python
113import os
114from dashscope import VideoSynthesis
115
116task = VideoSynthesis.async_call(
117 model=req.get("model", "wan2.6-i2v-flash"),
118 prompt=req["prompt"],
119 img_url=req["reference_image"],
120 duration=req.get("duration", 4),
121 fps=req.get("fps", 24),
122 size=req.get("size", "1280*720"),
123 api_key=os.getenv("DASHSCOPE_API_KEY"),
124)
125
126final = VideoSynthesis.wait(task)
127video_url = final.output.get("video_url")
128```
129
130## Operational guidance
131
132- Video generation can take minutes; expose progress and allow cancel/retry.
133- Cache by `(prompt, negative_prompt, duration, fps, size, seed, reference_image hash, motion_strength)`.
134- Store video assets in object storage and persist only URLs in metadata.
135- `reference_image` can be a URL or local path; the SDK auto-uploads local files.
136- If you get `Field required: input.img_url`, the reference image is missing or not mapped.
137- `wan2.6-t2v` and `wan2.6-t2v-us` add multi-shot narrative support and optional audio input according to the official docs.
138
139## Size notes
140
141- Use `WxH` format (e.g. `1280*720`).
142- Prefer common sizes; unsupported sizes can return 400.
143
144## Output location
145
146- Default output: `output/aliyun-wan-video/videos/`
147- Override base dir with `OUTPUT_DIR`.
148
149## Anti-patterns
150
151- Do not invent model names or aliases; use official Wan i2v model IDs only.
152- Do not block the UI without progress updates.
153- Do not retry blindly on 4xx; handle validation failures explicitly.
154
155## Workflow
156
1571) Confirm user intent, region, identifiers, and whether the operation is read-only or mutating.
1582) Run one minimal read-only query first to verify connectivity and permissions.
1593) Execute the target operation with explicit parameters and bounded scope.
1604) Verify results and save output/evidence files.
161
162## References
163
164- See `references/api_reference.md` for DashScope SDK mapping and async handling notes.
165
166- Source list: `references/sources.md`