dLazy Suno Music Generation

Problem It Solves

Suno music targets workflows that need complete songs from lyrics, style descriptions, or reference material. Instead of manually stitching together prompts, vocals, accompaniment, and export steps, it wraps the generation request into a single dlazy suno.music client call. This lets engineers or agents invoke dLazy-hosted Suno music generation from scripts and CLI pipelines.

How It Works

The skill is a thin client over the dLazy hosted API:
- Sends prompts, style settings, and vocal parameters to api.dlazy.com for inference.
- Uploads local audio, image, or video paths to files.dlazy.com before generation when supplied.
- Returns hosted output URLs from the API; with --no-wait, it returns an async task ID for later status polling.
It uses a dLazy API key from environment variables or CLI configuration, and accepts pipe references such as @N.path or @* to pull parameters from upstream output. Failures map to clear states: unauthorized, missing parameter, insufficient balance, server failure, or safety-policy rejection.

Boundaries

This is useful for automating Suno song generation, but it is not local inference: prompts and uploaded assets are processed through dLazy cloud services, and output URLs are hosted on dLazy media storage. For production use, verify account credits, API key permissions, content policy, and service terms. For one-off generation, run the command directly; for batch work, handle async polling, retries, and output archiving.