Music video API cost: quote, preflight, and control an MV budget

An OmnAPI music video does not have one universal per-video price. The accepted source duration, generation version, resolution, references, and optional processing determine the quote. Use a lightweight quote for planning, then preflight the actual media and authorize the paid create with maxCredits.

This guide was checked against the MV Fast quickstart and MV contract on September 18, 2026. It describes billing and integration behavior, not measured latency or output quality.

Choose the workflow before comparing prices

Workflow	Selection and boundary
MV Fast, OneClick V1	Default managed version; 10–600 seconds; 540p, 720p, or 1080p. High quality and lip-sync require at least 720p.
MV Fast, Premium V2	Explicit generation.managedVersion: "premium-v2"; 10–300 seconds at 720p, with version-specific performance and image requirements.
MV Studio	Editable storyboard and scene workflow. Budget for the stages, edits, and finalization you actually request.
Vidu Direct	Individual media operations with their own inputs and quote; not interchangeable with an end-to-end MV.

Premium V2 is opt-in and does not fall back to V1. Read the Premium V2 mode matrix before collecting portraits or setting performance modes. Do not copy V1 quality and lipSync options into a V2 request.

Use quote and preflight for different jobs

POST /api/v1/mv/quote estimates cost from the supplied settings. It does not validate remote audio or image files. Its result includes credits, an expiry, and a breakdown. Adding generated visual references, lip-sync, or other processing can change that breakdown.

POST /api/v1/mv/preflight checks the actual source and references, resolves duration, and returns a preflightId. It does not create a task or charge credits. A source URL that opens in your browser can still fail server-side validation because it requires a session, expires too soon, or serves an unsupported file.

For an external audio source, use source.type: "audio" and provide a reachable audio URL. The service checks the real duration; a guessed durationSec is not a way to lower the bill. For a supported Suno source, use the documented Suno source shape. A Producer clip ID is not a Suno clip ID.

Keep the validated request and budget together

Before a Fast batch, read GET /api/v1/mv/fast/availability for the selected managed version. An unavailable admission gate can reject creation before charging; use the documented retry interval instead of submitting repeatedly.

A robust create sequence is:

1. Store the desired media and generation options in your project.
2. Quote those options, including visual reference generation where applicable.
3. Preflight the actual create body and review warnings.
4. Present the validated cost and your application's spending policy to the user.
5. Create with the matching body, preflightId, applicable quoteId, maxCredits, and a persisted Idempotency-Key.
6. Store the receipt's taskId, stable mvId, and creditsRequired before leaving the request handler.

The create-time budget guard prevents accepting a request above the authorized credit ceiling. It is not permission to change the source or generation options while reusing an old preflight. Revalidate changed media. Requote an expired estimate. An insufficient-credit rejection is different from a media validation problem.

Do not silently regenerate an idempotency key after an HTTP timeout. Recover the original operation first. Each deliberate new video or scene edit is a separate business operation and may incur another charge.

Account for subtitles and reference images

Lyrics text provides planning context, not guaranteed timing. For controlled subtitle timing, supply the documented SRT input. The current MV contract also supports automatic subtitle extraction with explicit mode, budget, and fallback settings. Review the selected subtitle strategy in the quickstart.

A character image is an identity reference. It does not guarantee that a person appears in every shot, wears one fixed outfit throughout synthesized planning, or sings without the appropriate performance configuration. Additional reference synthesis can add cost; use the quote fields corresponding to the actual create settings.

For Studio or scene-edit workflows, include regeneration and recomposition in the project budget. A low cost for one scene is not the cost of a reviewed final music video.

Recover and deliver the final file

Poll the task until terminal and read the MV using its mvId. The existence of that ID is not a readiness signal. GET /api/v1/mv/{mvId}/final reports whether the final is ready and returns a fresh temporary videoUrl when available.

After scene edits, the previous final can become stale. Inspect staleReason, retryable, and actionHint; when the contract calls for recomposition, finalize the new composition before publishing it. Save accepted MP4 files in storage you control.

Measure cost per accepted output

For an internal evaluation, record the quoted and charged credits, source duration, settings, time to completion, terminal outcome, and whether the result passes your review. Separate base generation, revisions, subtitles, reference generation, and file storage. Use the actual paid credit package and checkout fee when converting credits to money.

This produces a meaningful comparison across your own workload. It does not justify claims about universal success rates or being cheaper than another service without matched tests and current prices.

Continue with MV product details, the complete quote-to-download quickstart, or pricing. To generate the source song first, use the Producer workflow.