The Mureka V9 API turns lyrics into finished songs through one async REST call on reAPI. Send your text, optional style prompt, and get up to three rendered mp3, wav, or flac tracks from the Mureka V9 model.
Required, up to 3000 characters
Optional, up to 1024 characters
1, 2, or 3
mp3, wav, or flac
Optional, Mureka-issued
Optional, Mureka-issued
Optional, Mureka-issued
Credit-based — 1 credit = $0.001 USD. Pay only for completed generations.
One sample at the cheapest tier (per song).
Mureka V9 is Mureka's lyrics-to-song model, exposed on reAPI as one async endpoint that turns up to 3000 characters of lyrics into a fully produced track, steered by an optional style prompt of up to 1024 characters and optional reference, vocal, or melody IDs. A single request returns one to three songs as mp3, wav, or flac, billed per song.
Real-world workflows and production use cases you can build and ship with this model.
Songwriting tools and lyric editors plug the Mureka V9 API into their compose flow. Users type lyrics, hit generate, and hear a finished version of their idea. Because the Mureka V9 API is async, your UI shows a polling state instead of blocking the editor while the render runs. Store the returned task id with the lyric draft so users can replay the same Mureka V9 API output later.
Generate with Mureka V9
Video editors, podcast tools, and short-form creator products use the Mureka V9 API to score scenes without licensing stock music. Send the script as lyrics, add a style prompt, drop the resulting track into the timeline. Set number_of_songs to 3 and let editors pick the best take in one Mureka V9 API call. The Mureka V9 API returns clean mp3, wav, or flac so editors can normalize, trim, or master downstream.
Music product teams use the Mureka V9 API as a fast prototyping channel. Same lyrics, different style prompts, then compare the takes side by side. Adding a reference_id or melody_id anchors the Mureka V9 API on a known-good arrangement while you tune lyric variations. Store the task id with the input so any Mureka V9 API track is reproducible later without re-sending lyrics over the network.
Many text-to-music APIs only take a prompt and paraphrase the result. The Mureka V9 API on this page accepts the actual lyrics, so vocals follow your words, not an interpretation. That matters for any product where the user owns the words.
One Mureka V9 API call returns one, two, or three versions of the same lyrics. Pricing rises linearly with number_of_songs, while the submit-and-poll flow stays a single async task. Queue logic and cost both stay predictable for your backend.
The Mureka V9 API returns a task id you can store before any audio exists. Wire that id to your internal job or session record. When the task finishes, the same id resolves to the rendered URLs, so download flows stay aligned with the original Mureka V9 API request.
Both engines generate AI songs from text. The Mureka V9 API leans on lyrics-first generation and Mureka-issued reference IDs for controllable production work, which is how this page recommends pairing it with developer integrations evaluating a Suno alternative API.
Comparison reflects publicly documented behavior at the time of writing. Run the Mureka V9 API against your real lyrics in the playground above for a direct, evidence-based read.
Generate a reAPI key in workspace settings. The same key calls the Mureka V9 API and every other reAPI image, video, and audio endpoint.
OpenPOST to /api/v1/audio/generations with model mureka-v9-song, your lyrics, and an optional style prompt or reference IDs. The Mureka V9 API returns a task id immediately.
OpenGET /api/v1/tasks/:id until status is completed. Read output.audio_urls for the rendered tracks. Each Mureka V9 API task keeps its URLs reachable once it finishes.
Opencurl https://reapi.ai/api/v1/audio/generations \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model":"mureka-v9-song","lyrics":"Verse 1...\\nChorus...","prompt":"Emotional pop ballad with piano, warm strings, polished modern production","number_of_songs":1,"output_format":"mp3"}'Rejected synchronously with the failing field named. Check enum values, ranges, and URL fields — nothing is charged.
401 means a missing or invalid Bearer key; 402 means the reserve exceeds your balance. Manage keys and credits in the console.
Reference material and outputs pass automated moderation. Rejected tasks fail with a clear error and a full refund.
A task that reaches a failed state is never charged — the reserve refunds automatically. Keep the task id and retry when ready.
Common questions about this model.
Try it in the playground or grab an API key to integrate now.
