Vidu video

Use this skill to design a production request or integration for the Vidu Open Platform API. Default to dry-run planning. Never submit a paid generation, upload private media, cancel a task, or download a result until the operator has approved the exact provider, endpoint, model, inputs, request digest, maximum charge, storage destination, and disclosure plan.

This document was verified against first-party public documentation on 2026-07-10. Models, prices, accepted fields, policies, and availability are volatile; re-open the linked endpoint and pricing pages immediately before execution.

Keep the surfaces separate

• Open Platform API: https://api.vidu.com, API keys, organization-level limits, asynchronous tasks, and API credits. This is the surface covered here.
• Vidu consumer product: https://www.vidu.com and its subscription/plan credits. Do not assume its credits, features, watermark behavior, or terms apply to the API.
• Vidu-S1 (Beta): a separate interactive digital-human product using HTTP session setup, AliRTC media, and WebSocket control. It is not a Q3/Q2 clip model. Its public page currently mixes “1 minute to 2 hours” marketing language with a 600-second session maximum. Its pricing section separately says 3 S1 credits per 2 seconds, lists a 0.03125 credit unit price, deducts every 6 seconds, rounds to 2-second intervals, and requires at least 45 credits to create a session. Do not revalue those statements using the clip API's $0.005 credit price without written confirmation.
• S1 documentation conflict: Step 3 says browser WebSocket authentication belongs in the URL query because browsers cannot set custom headers, while the page's Important Notes says it must be in an authorization header. Treat this as unresolved. Confirm the current transport with Vidu before implementation, never place a bearer URL in logs/analytics/referrers, and do not infer a secure browser design from the sample alone.
• China host: the S1 page documents api.vidu.cn for China and api.vidu.com internationally. The ordinary clip endpoints documented here use api.vidu.com; do not infer compute residency from the hostname.

Choose a mode first, then a model

The endpoint contract is more authoritative than a family name. A model may exist without supporting every mode.