Explicit submission inputs
Audio, references, prompt, model, and aspect ratio remain visible as arguments that can be reviewed before execution.
Use BizMuse CLI with
Submit tracks, attach visual references, check task status, and retrieve finished assets without leaving your shell.
Terminal command
Get API Keynpm install -g bizmuse-cliPrepare a repeatable terminal workflow
- 01
Install the CLI
Install BizMuse CLI globally so the same command is available in local shells and automated runners.
Terminal commandnpm install -g bizmuse-cli - 02
Authorize this machine
Save your BizMuse API key once. Later commands reuse the local credential without exposing it in shell history.
Terminal commandbizmuse auth set-api-key - 03
Submit your first task
Choose a soundtrack, references, format, and direction explicitly, then keep the returned task ID for status checks.
Terminal commandbizmuse mv run --audio song.mp3 --prompt "..."
A focused CLI for reliable tasks
A clear task lifecycle
Submit, status, and result commands separate task submission from long-running render work.
Local and remote media
Use filesystem paths during hands-on work or direct media URLs inside hosted automation environments.
Structured reference inputs
Pass ordered image references without burying asset names or intent inside an unstructured prompt.
Format chosen up front
Set the target composition at submission time so downstream publishing does not depend on emergency cropping.
Machine-readable task output
Task IDs, status details, and result payloads remain structured so scripts can store and pass them between steps.
Where the CLI fits
Local production utilities
Run a render task alongside media preparation scripts, naming checks, and release packaging commands.
Content teams with review queues
Submit approved tracks from a review queue and retain each task ID for editorial follow-up.
Scheduled media pipelines
Use structured results to pass finished assets to storage, cataloging, or notification systems.
Export-to-video workflows
Take a mastered or AI-generated audio export and move it into video production with reproducible settings.
CLI operating notes
What does the CLI control?
It covers authentication, generation submission, task inspection, and result retrieval for BizMuse music video tasks.
What must be installed locally?
Use a supported Node.js environment, the BizMuse CLI package, and a valid BizMuse API key for the account that owns the tasks.
Can I use the CLI in automation?
Yes. Keep submission inputs explicit, persist the returned task ID, and let later steps inspect status and retrieve the completed result.
Can a command read platform page URLs?
No. Provide an audio file path or direct media URL. Export tracks from music platforms before submission.
Should a script wait for the finished video?
Usually not. Capture the task ID, poll status at a sensible interval, and retrieve assets only after the task reports completion.
Which output format should automation use?
Use the --json option for task IDs, progress, errors, video URLs, and cover metadata instead of parsing terminal text.
Bring BizMuse into your shell workflow
Install the CLI, authorize the machine, and submit a test track with settings you can reuse in scripts.
Get StartedFree to start, no credit card