Mureka AI Upload Audio is a fast audio upload utility that creates a reusable Mureka upload ID from an audio URL via the official Mureka API. Ready-to-use REST inference API for audio asset preparation, AI song generation, vocal cloning workflows, reference audio management, music production, creative audio projects, and professional music workflows with simple integration, no coldstarts, and affordable pricing.
Bezczynny
{
"id": "140567225040898",
"purpose": "audio",
"audio_id": "140567225040898"
}$0.01za uruchomienie·~100 / $1
Mureka AI Create Upload ID is a utility workflow that uploads an audio file to the Mureka system and returns a reusable Mureka asset ID for downstream generation tasks. It is designed for preparing reference audio, melody inputs, vocal inputs, remix assets, and other reusable audio resources across the Mureka model ecosystem.
Reusable Mureka asset IDs Upload an audio file once and reuse the returned ID in compatible Mureka workflows.
Purpose-based asset preparation
Choose the intended asset type with purpose, such as audio, instrumental, melody, reference, remix, vocal, or voice.
Simple upload workflow Provide one audio file, choose a purpose, and receive a reusable ID with minimal setup.
Useful across Mureka pipelines Helps prepare audio inputs for song generation, vocal workflows, melody guidance, and reference-based music tasks.
Production-ready API Suitable for asset preparation, reusable audio management, and larger Mureka music production pipelines.
| Parameter | Required | Description |
|---|---|---|
| audio | Yes | Source audio file to upload into the Mureka system. |
| purpose | No | Intended asset type for the uploaded audio. Supported values: audio, instrumental, melody, reference, remix, vocal, voice. Default: audio. |
{
"id": "140567225040898",
"purpose": "audio",
"audio_id": "140567225040898"
}
Just $0.01 per request.
purpose does not affect pricingpurpose so the returned asset is easier to reuse in the right downstream workflow.audio is required.purpose defaults to audio.This model accepts public audio file URLs through the audio field. Keep the field name as audio for API compatibility.
Supported formats: .mp3, .m4a.
Available purposes: audio, instrumental, melody, reference, remix, vocal, voice.
melody can also support .mid in the backend, but the frontend uploader is configured for audio files only. Non-audio purposes such as lyrics-video and soundtrack are not exposed here because they require image or video uploads.
Grab a WaveSpeedAI API key, then call POST https://api.wavespeed.ai/api/v3/mureka-ai/create-upload-id with your input as JSON. The endpoint returns a prediction id; poll the prediction endpoint until status flips to completed, then read the output URL from data.outputs[0]. Examples for Create Upload Id below.
# Submit the prediction
curl -X POST "https://api.wavespeed.ai/api/v3/mureka-ai/create-upload-id" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $WAVESPEED_API_KEY" \
-d '{
"audio": "https://example.com/your-audio.mp3",
"purpose": "audio"
}'
# Response includes a prediction id. Poll for the result:
curl -X GET "https://api.wavespeed.ai/api/v3/predictions/{request_id}/result" \
-H "Authorization: Bearer $WAVESPEED_API_KEY"
# When status is "completed", read the output from data.outputs[0].// npm install wavespeed
const WaveSpeed = require('wavespeed');
const client = new WaveSpeed(); // reads WAVESPEED_API_KEY from env
const result = await client.run("mureka-ai/create-upload-id", {
"audio": "https://example.com/your-audio.mp3",
"purpose": "audio"
});
console.log(result.outputs[0]); // → URL of the generated output# pip install wavespeed
import wavespeed
output = wavespeed.run(
"mureka-ai/create-upload-id",
{
"audio": "https://example.com/your-audio.mp3",
"purpose": "audio"
}
)
print(output["outputs"][0]) # → URL of the generated outputCreate Upload Id is a Mureka Ai model for AI inference, exposed as a REST API on WaveSpeedAI. Mureka AI Upload Audio is a fast audio upload utility that creates a reusable Mureka upload ID from an audio URL via the official Mureka API. Ready-to-use REST inference API for audio asset preparation, AI song generation, vocal cloning workflows, reference audio management, music production, creative audio projects, and professional music workflows with simple integration, no coldstarts, and affordable pricing. You can call it programmatically or try it from the playground above.
POST your input parameters to the model's REST endpoint (shown in the API tab of this playground) with your WaveSpeedAI API key in the Authorization header. Submission returns a prediction ID; poll the prediction endpoint until status flips to "completed", then read the output URL from the result. The playground generates a ready-to-paste code sample in Python, JavaScript, or cURL for whatever inputs you've set. Full request/response shape is documented at https://wavespeed.ai/docs/docs-api/mureka-ai/mureka-ai-create-upload-id.
Create Upload Id starts at $0.010 per run. That figure is the base price — the final charge scales with the parameters you set in the form (output size, length, count, references, or whatever knobs this model exposes), so a higher-quality or larger output costs more than a minimal one. The exact cost for your current input is shown live next to the Generate button before you submit, and the actual per-call charge is recorded on the prediction afterwards.
Key inputs: `audio`, `purpose`. The full JSON schema (types, defaults, allowed values) is rendered above the Generate button and mirrored in the API reference at https://wavespeed.ai/docs/docs-api/mureka-ai/mureka-ai-create-upload-id.
Sign up for a free WaveSpeedAI account to claim starter credits, copy your API key from /accesskey, then call the endpoint shown in the API tab of the playground. The playground also auto-generates a code sample in Python, JavaScript, or cURL for the parameters you've set.
Commercial usage rights depend on the model's license, set by its provider (Mureka Ai). The license summary appears on the model card above; see WaveSpeedAI's Terms of Service for platform-level conditions.