Mureka V9 Song API

Use mureka-v9-song to turn written lyrics into one or more fully produced songs. Each call is asynchronous: submit the task, poll for completion, then fetch the rendered audio from the returned URLs.

Endpoint

POST /api/v1/audio/generations

Poll completion with:

GET /api/v1/tasks/{id}

The task stays in processing until the song is rendered; final URLs land in output.audio_urls when the status flips to completed.

Example

curl https://reapi.ai/api/v1/audio/generations \
  -H "Authorization: Bearer $REAPI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "mureka-v9-song",
    "lyrics": "Verse 1...\nChorus...\nVerse 2...",
    "prompt": "Emotional pop ballad with piano, warm strings, cinematic chorus, expressive female vocal, polished modern production",
    "number_of_songs": 1,
    "output_format": "mp3"
  }'

Parameters

The three reference IDs are minted by Mureka's own upload system. ReAPI forwards them verbatim and does not proxy uploads — bring an ID you already have, or omit them entirely for fully generated songs.

Output

Successful tasks return one URL per generated song in output.audio_urls. With number_of_songs: 3 the array contains three URLs, all in the same format selected by output_format.

Pricing

Billed per generated song. Only number_of_songs affects pricing — prompt, output_format, and the three reference IDs are free to use. See current rates on the Mureka V9 model page.

Tips

• Structure lyrics with clear Verse / Chorus / Bridge blocks for better arrangement.
• Use the style prompt to pin genre, tempo, and vocal character — Mureka follows these strongly.
• Set number_of_songs > 1 when you want quick variations from the same lyrics.
• Use a reference ID only when you want the model to track a specific vocal or melody — without one it composes freely from the lyrics + prompt.
• Stick with mp3 while iterating; switch to wav or flac for final mastering.