Doubao Seedance 1.5 Pro Dance Video Generator

Problem

When a static character image, pose sheet, or motion reference needs to become a playable dance clip, prompt writing alone is not enough: the workflow also has to handle cloud API authentication, media uploads, async task polling, and error cases such as missing credits or safety-policy rejections. seedance 1.5 pro packages this flow as a thin client around the dLazy CLI, aimed at engineers and automation pipelines.

How It Works

The skill invokes the hosted Doubao Seedance 1.5 Pro API through this path:
- Run dlazy seedance-1.5-pro to start generation;
- Prompts and parameters are sent to api.dlazy.com for inference;
- Local image, video, or audio file paths are uploaded to dLazy media storage so the model can read them;
- Results are usually output URLs hosted on files.dlazy.com;
- In --no-wait mode, the response contains outputs: [] plus a task status object, so the caller must keep polling.

It supports dLazy API key authentication, and the key can also be provided through DLAZY_API_KEY. Error semantics are explicit: 401 indicates a missing or invalid key, 501 means --prompt is missing, 502 points to a local file read problem, 503 covers insufficient balance or server errors, and 504 can report async task failure with a backend reason such as a safety-policy violation.

Boundaries

This is useful for automated dance or action video generation, but it should not be treated as local inference, private deployment, or a full video-editing system. Because media files are uploaded to dLazy's cloud, sensitive assets need compliance review first. When failures are caused by balance, credentials, or safety policies, handle the returned code explicitly instead of blindly retrying.