Mureka API Guide: AI Music Generation, Pricing & Code (2026)

Mureka has been quietly building a reputation as the fast, budget-friendly option in AI music generation, the one you reach for when you need a lot of tracks without much setup. It doesn't get the same attention as Suno or Udio, but it has a real developer API behind it, and how that API actually works isn't well documented outside Mureka's own site. Here's what it does, what it costs, and how to call it.

What Is Mureka

Mureka is an AI music generation platform that turns text prompts or full lyrics into finished songs, complete with vocals and instrumentation, or instrumental-only tracks when you don't want vocals at all. It sits in the same category as Suno and Udio, both of which already have standalone guides on the Apiframe blog, and the three get compared directly in our AI music API comparison post. The short version of that comparison: Mureka trades a bit of vocal polish for speed and lower cost per track, which makes it a strong pick for high-volume or budget-sensitive use cases rather than a flagship consumer music product.

Mureka API Access and Authentication

Mureka's developer API is a separate product from its consumer web app. Signing up on the Mureka website doesn't give you API access (and vice versa); the two are billed and managed independently. To get API access:

1. Sign up for an account on the Mureka developer platform.

2. Open the "API Keys" tab in your dashboard to create and manage keys.

3. Fund your account, since Mureka's API runs on a prepaid top-up balance rather than a subscription (more on that below).

Every request goes to https://api.mureka.ai and needs your key in the Authorization header as a bearer token:

Authorization: Bearer MUREKA_API_KEY

Keep the key server-side. Mureka's own docs are explicit that it shouldn't be exposed in browser or client-side code.

Mureka API Features

Mureka's API is broken into several distinct endpoints rather than one catch-all "generate" call, which is worth knowing before you start integrating:

Lyrics to song (POST /v1/song/generate): generate a full song when you supply your own lyrics.

Prompt to song (POST /v1/song/easy-generate): generate a full song from a style prompt alone, letting Mureka write the lyrics for you.

Generate instrumental (POST /v1/instrumental/generate): instrumental-only tracks, no vocals.

Generate lyrics / Extend lyrics: standalone lyric generation and extension, useful if you want to review or edit lyrics before generating audio.

Extend song, Remix, Region editing, Stem song, Vocal cloning, Music transcription, and a few other specialized endpoints for post-processing existing tracks.

For genre, mood, and vocal style, you steer generation with a style prompt (for example, "r&b, slow, passionate, male vocal"), the same style-description approach Suno and Udio use.

Mureka API Pricing

This is the area where Mureka is the least transparent among the major music APIs, and it's worth flagging clearly rather than glossing over it. There's no public flat-rate card showing a fixed price per song. Instead, according to Mureka's own API platform documentation:

Access runs on a prepaid top-up balance, not a recurring subscription. You buy credit, and it's consumed gradually as you generate.

Your balance stays valid for 12 months from your last recharge, and any new recharge extends the validity of your existing balance too.

How many tracks you can generate at the same time scales up with your top-up tier — a larger balance unlocks more simultaneous generations.

Downloading generated songs is free. The multitrack stems feature is the one thing that requires a separate payment on top of generation.

All credits are non-refundable, both purchased and bonus credit, once spent or once the validity window lapses.

Because Mureka doesn't publish a fixed per-song rate publicly, the honest move here is to check current top-up pricing directly on your platform dashboard before budgeting a feature around it, or see how Mureka stacks up against other music APIs on price, rather than relying on a number that may already be stale by the time you read this. If you want a single-vendor API with a public, fixed per-song credit cost instead, Apiframe prices Mureka generations at 7 credits ($0.07) per song regardless of how Mureka's own top-up tiers are structured, which can make budgeting simpler if unpredictable API pricing is a dealbreaker for your project.

Code Example: Generating a Track with Mureka

Mureka does not generate tracks instantly. You send a request, get back a task ID and a preparing status, then keep checking a query endpoint until the track is ready. Here's how that looks in Python:

import requests
import time

API_KEY = "YOUR_MUREKA_API_KEY"
headers = {
    "Authorization": f"Bearer {API_KEY}",
    "Content-Type": "application/json",
}

# 1. Submit the generation request
submit = requests.post(
    "https://api.mureka.ai/v1/song/generate",
    headers=headers,
    json={
        "lyrics": "[Verse]\nIn the stormy night, I wander alone\nLost in the rain, feeling like I have been thrown",
        "model": "auto",
        "prompt": "r&b, slow, passionate, male vocal",
    },
)
task = submit.json()
task_id = task["id"]

# 2. Poll the task until it's no longer preparing
query_url = f"https://api.mureka.ai/v1/song/query/{task_id}"
while True:
    task = requests.get(query_url, headers=headers).json()
    if task["status"] != "preparing":
        break
    time.sleep(5)

print(task)

If you'd rather skip writing lyrics yourself, swap the request to POST /v1/song/easy-generate and drop the lyrics field. For instrumental-only output, use POST /v1/instrumental/generate instead. Every response includes a trace_id, worth logging in production since it's what Mureka's support team will ask for if you need to debug a failed generation.

Error responses return an HTTP status of 400 or higher with a body like {"error": {"message": "..."}, "trace_id": "..."}. Common ones to handle: 401 for a bad key, 429 for either hitting your concurrent request limit or running out of credit, and 503 when Mureka's generation engine is overloaded and you should retry after a short wait.

Mureka vs Suno vs Udio: Quick Take

Mureka's core tradeoff is speed and cost against vocal polish. It generates tracks faster and, based on Mureka's top-up pricing, tends to run cheaper per track than Suno or Udio, but vocal quality is noticeably behind the top two in refinement. That makes it a reasonable default for high-volume, budget-sensitive use cases like background music for short-form video at scale, and a less obvious choice for a consumer-facing product where vocal quality is the main selling point. For the full breakdown on licensing, genre range, and audio quality across all three, see our AI Music API Compared: Suno vs Udio vs Mureka post.

How much does Mureka cost per track?Mureka doesn't publish a fixed public rate. Access runs on a prepaid credit balance that you top up, with the number of simultaneous generations you can run goes up as you top up more, so check current pricing on your dashboard before budgeting. Providers like Apiframe that offer Mureka through a unified API publish a flat per-song credit cost of 7 credits ($0.07) instead.