Overview
Wan 2.2 Animate is an Alibaba video model for character animation and character replacement. Use this page when you are ready to call the API after trying the model in the APIXO playground.Endpoint and authentication
Base URL:
All requests require your APIXO API key:
Copy-paste async quickstart
This minimal request submits an animate task and returns ataskId.
taskId; you need it to poll for the final result.
Poll for result
resultJson after state becomes success:
Request body
Animate
Usetype: "animate" to animate the character in the source image with motion from the reference video.
Replace
Usetype: "replace" to replace the character in the motion video with the character from the source image.
Parameters
Result delivery mode. Use
async for polling with statusTask, or callback for webhook delivery.Required when
request_type is callback. Must be a public HTTPS URL that can receive the final task payload. See Webhooks.Response format
Submit task response
POST /generateTask/wan-2-2-animate returns a task ID when the task is accepted:
Status response fields
Processing duration in milliseconds. Present after successful completion when timing data is available.
Webhook callback mode
Use callback mode when your backend should receive the final result automatically instead of polling.Billing
New non-LLM requests use 1 credit =$0.001. Calculate the full amount, including billable quantity and add-ons, apply the applicable account discount, then round the request total upward to the next whole credit. Agreed fixed unit prices retain their precision and replace the standard price and discount; final rounding still applies. See credit conversion and rounding.
Wan 2.2 Animate is billed per generated video second. The selected resolution determines the unit price, and billable duration is detected from video_urls[0].
If the reference video is shorter than 5 seconds, billing uses 5 seconds. If it is longer than 120 seconds, billing is capped at 120 seconds.
For current API rates in USD, see API pricing.
Latency and polling
Actual latency may vary by reference video duration, resolution, queue load, and current route health.
Rate limits and concurrency can vary by account, API key, and route. If you receive
429, slow down requests and retry with backoff. For account-level details, see System APIs.
Errors and troubleshooting
HTTP errors
Task failure causes
Common fixes
See Error Codes for the full error reference.
MCP integration
The complete model schema declares result decoding inmcp.result and supported file bindings in mcp.attachments. These are client integration metadata, not generation input parameters. Attachment paths: image_urls, video_urls. Preserve the user’s file order. Model parameter validation remains on the API.