alibaba-wan-video

What it does

Plan, implement, and review Alibaba Wan video generation using Alibaba Cloud Model Studio/DashScope hosted APIs or official Wan 2.1/2.2 open-weight checkpoints. Use for Wan text-to-video, image-to-video, first/last-frame or continuation, reference-to-video, video editing, speech-driven video, character animation, regional deployment, billing, licensing, and production safety.

How it works

• Route first: gather task inputs (duration/resolution/aspect, audio, region/data boundary, budget, latency, GPU, managed inference).
• Choose one route: Hosted Model Studio for Wan 2.7 quality and capabilities (2–15 second clips, generated audio, 1080P, reference-to-video, continuation, hosted editing), or Official open weights for offline processing and self-hosting. Do not substitute hosted aliases or older APIs.
• Before billable requests, show exact model/revision, region, inputs, output settings, estimated charge/storage, and obtain explicit approval; a dry run must not mutate network state.
• Keep product families separate in a provided comparison table, with explicit model IDs and capabilities for Hosted Wan 2.7, Hosted Wan 2.6, Open Wan 2.2, and Open Wan 2.1.
• Wan 2.7 request shapes: provide Create and Poll endpoints, required headers, and task lifecycle states; download MP4/H.264 outputs; pay attention to regional endpoints and authenticated access.
• Include example core T2V body with model and input/parameters, and note language support, prompt limits, duration, resolution, ratio, and watermark defaults.
• Provide additional examples for First/Last Frame I2V, Continuation, and Reference-to-video usage with specific models and media payloads.
• Include constraints for I2V and R2V inputs/outputs, plus media size limits and duration behavior, and remind re-check of API pages for volatile constraints.
• Provide a dry-run/two-step billable workflow Python example that pins region, prints a redacted plan, validates constraints, and ensures safe handling.

When to use it

Use when planning or executing Wan video generation tasks that must be hosted (Model Studio) or offline/self-hosted with Wan 2.1/2.2 open weights. Use the hosted route for current Wan 2.7 quality and features (2–15 second clips, reference-to-video, editing, etc.). Use open weights for offline processing, reproducible checkpoints, or self-hosting. Rules emphasize explicit approval before billable actions and careful region/workspace configuration.

What it can touch

• API endpoints for Wan 2.7 (Create and Poll) under hosted DashScope endpoints
• Model identifiers like wan2.7-t2v-2026-06-12, wan2.7-i2v-2026-04-25, wan2.7-r2v-2026-06-12, wan2.7-videoedit
• Region-specific endpoints and workspace domains as documented
• Media payloads including input prompts, media references, and parameters such as resolution, duration, ratio, watermark, and seed
• JSON payload structures for core T2V, I2V, and R2V operations
• Python snippet scaffolding for dry-run and billing guardrails

Caveats

• Explicitly states to show model/revision, region, inputs, output settings, estimated charges, and obtain explicit approval before any billable request or large checkpoint download
• Warns that SDKs for Wan 2.7 have different minimum versions across languages; verify versions before pinning dependencies
• Notes that task query results and signed video URLs expire after 24 hours; download promptly
• Indicates that Hosted Wan 2.7 is a closed managed service under Model Studio terms; no hosted Wan 2.7 checkpoint is implied by API name
• Contains price references and region constraints that are volatile and require rechecking against first-party pages at execution