Wan on RunAPI

Generate and edit video with Wan through RunAPI. The default path for one-off agent tasks is the runapi CLI; SDKs are for application integration.

Routing decision

• One-off generation, editing, or transformation for the user → use the CLI path with the runapi binary.
• Building an app, backend, worker, library, or production codebase → use the SDK integration path.

CLI path

The runapi binary is the runtime dependency. Authenticate with runapi login (browser) or set RUNAPI_API_KEY; a saved CLI config also works — no required environment variable.

Inspect the available actions and request fields with CLI help:

runapi wan --help
runapi wan text-to-video --help

Run a one-off task (synchronous — polls until the task completes):

runapi wan text-to-video --input-file request.json

Submit asynchronously and poll separately:

runapi wan text-to-video --async --input-file request.json
runapi wait \x3Ctask-id> --service wan --action text-to-video

Available actions: text-to-video, image-to-video, video-to-video, speech-to-video, animate, text-to-image, reference-to-video, edit-video.

SDK integration path

When integrating Wan into an app, backend, worker, or library — not for one-off tasks — use a RunAPI SDK package:

• JavaScript / TypeScript: @runapi.ai/wan
• Ruby: runapi-wan
• Go: github.com/runapi-ai/wan-sdk/go

References

• Model overview, pricing, and rate limits: https://runapi.ai/models/wan.md
• Provider comparison: https://runapi.ai/providers/alibaba.md
• Full model catalog: https://runapi.ai/models.md

Variants

• 2.2 A14B text to video turbo
• 2.2 A14B image to video turbo
• 2.2 A14B speech to video turbo
• 2.2 animate move
• 2.2 animate replace
• 2.5 text to video
• 2.5 image to video
• 2.6 text to video
• 2.6 image to video
• 2.6 video to video
• 2.6 flash image to video
• 2.6 flash video to video
• 2.7 text to video
• 2.7 image to video
• 2.7 image
• 2.7 image pro
• 2.7 reference to video
• 2.7 video edit