Mureka V9 API

The Mureka V9 API is an async REST endpoint that turns written lyrics into a finished, vocal-led song. It exposes the Mureka V9 model from Mureka AI through reAPI, so one reAPI key gives your product lyrics-to-song without separate vendor onboarding. POST lyrics and an optional style prompt to /api/v1/audio/generations with model mureka-v9-song, then poll /api/v1/tasks/:id for the Mureka V9 API output.

Mureka V9 is the current generation of the Mureka music model and replaces earlier releases like V7 for new integrations. V9 ships with tighter vocal control and cleaner arrangement output. The Mureka V9 API on reAPI exposes this latest model under model id mureka-v9-song, so callers always hit the V9 generation without picking a version flag — and any future Mureka version upgrade slots in behind the same Mureka V9 API surface.

The Mureka V9 API is built around lyrics-first generation with optional Mureka-issued reference IDs for vocal and melody guidance, which is a more controllable surface for production integrations than a pure prompt-only flow. Both Mureka and Suno are mature AI music engines; pick the Mureka V9 API on reAPI when you want lyrics fidelity, three-output variants per call, and one reAPI key that already covers your image, video, and audio endpoints. If you are evaluating a Suno alternative API, the Mureka V9 API is worth a side-by-side test on your real lyrics.

Mureka V9 API pricing is per song, with rate tiers for one / two / three songs. Only number_of_songs affects Mureka V9 API cost — prompt, output_format, and the three reference IDs are free. See current per-song-count rates in the pricing table on this page. Estimate the cost in this page's playground before you ship, and keep the same accounting in your product.

The Mureka V9 API accepts plain-text lyrics up to 3000 characters. Structure them with line breaks for verses, choruses, and bridges so the arrangement follows the section flow. Multi-language lyrics work — the Mureka V9 API renders vocals in the target language. Avoid stage directions inside the lyrics; put musical direction in the optional style prompt instead.

All three IDs are minted by Mureka's own upload system. Bring an ID you already have from Mureka and pass it to the Mureka V9 API to pin overall style, a specific vocal performance, or a melody topline. reAPI forwards the IDs verbatim and does not proxy uploads, so the Mureka V9 API call stays a lightweight JSON request. Omit all three for a fully generated song shaped only by lyrics and prompt.

Render time depends on lyric length, prompt complexity, and number_of_songs — typically tens of seconds to a few minutes per Mureka V9 API task. Submit the task, save the returned task id, and poll /api/v1/tasks/:id until status is completed. Show a progress state instead of blocking on the Mureka V9 API render; users tolerate polling far better than a frozen submit button.

The full parameter table, cURL example, and response shape live at /docs/mureka-v9-song. POST /api/v1/audio/generations to create a Mureka V9 API job, GET /api/v1/tasks/:id to poll the result. The docs show the same model id, lyrics rules, and pricing tiers as this Mureka V9 API playground, so what you see here is what you ship in production.

Paid. Completed generations are charged at the rates in this page's pricing table. Eligible new accounts may receive promotional test credits; availability and amount are shown at signup or in the dashboard. Technical or provider failures are refunded automatically, except where this page documents a charged output-moderation block.

No. Pricing is pay-as-you-go: $1 buys 1,000 credits and credits never expire. Cost scales with what you generate rather than with a recurring fee.

Sign up and create a key in the dashboard, no card required. Pass it as a Bearer token in the Authorization header.