GPT Image 2.5 is live — OpenAI's newest image model, targeted edits that leave the rest of the frame alone

Music Extractor API

Extract background music from mixed audio. The music extractor API returns the music stem and a no_music remainder through one async task.

Highlights
Instrumental extraction · 7 splitter engines
Best for
Karaoke beds, background music
Input
Audio file URL
Output
Instrumental track
Input
0/1 file

MP3 / WAV / AAC / OGG

Default auto

Optional

mp3, wav, flac, aac, or ogg

Result

Pricing

Credit-based — 1 credit = $0.001 USD. Pay only for completed generations.

First test cost
$0.2200 credits

One sample at the cheapest tier (1 started minute).

Testing budget guide
Add credits
$10
≈ 50 tests
$50
≈ 250 tests
$100
≈ 500 tests
Source audio
$0.2
Price · 1 started minute

What you can build with this model

Real-world workflows and production use cases you can build and ship with this model.

music waveform isolated from mixed audio

Music extractor API for creator clips

Use the music extractor API when a clip combines speech, music, and room sound. Your app can keep the music stem for editing, cataloging, moderation, or reuse. The music extractor API works well for products that need the bed, not just a vocal split. It gives creator tools a clean way to save the soundtrack without asking users to export from an editor. The music extractor API is also useful when support teams need a repeatable backend job instead of manual audio cleanup.

Extract music
timeline with an extracted music bed ready for editing

Music extractor API for clean edit assets

Editors often need the bed without rebuilding the whole timeline. The music extractor API gives your workflow a downloadable music track and a no_music remainder from the same source. That pair lets a review tool compare the original mix against the extracted music bed. Teams can preview both outputs before approving a clip, archiving a sound bed, or sending the result to another workflow.

queue of async music extraction jobs

Batch-friendly music extractor API queues

Submit the music extractor API task, store the task id, and poll later. That flow works for creator tools, media archives, and review systems that process many clips at once. Each completed task returns URLs your app can store, preview, or hand to another service. The music extractor API lets backend queues process long clip libraries without keeping a browser tab open.

Why reAPI for Music Extractor API

Why this music extractor API uses one surface

The music extractor API submits the music model directly instead of asking users to choose a generic stem. That keeps the page, playground, and docs aligned with one job. Less choice here is intentional because the user already came to extract music.

Music plus remainder

Completed tasks can return a music stem and a no_music track. Your app can save both, preview both, or send either output into the next step. Keep both files when users may later need the original speech without the bed or the bed without the speech. The music extractor API makes that pair available from one task.

Music extractor API output you can reuse

Send an audio_url and keep binary uploads out of your backend request body. The music extractor API handles processing asynchronously and returns downloadable output URLs. Your product can save those URLs with the task record or move them into its own storage after completion.

Integrate the music extractor API in three steps

  1. step 01

    Create an API key

    Generate a reAPI key from workspace settings. Use it to call /api/v1/audio/generations from your backend.

    Open
  2. step 02

    Submit a music extraction task

    POST model audio-music-extractor with a public audio_url. Add encoder_format when your product needs a specific output container.

    Open
  3. step 03

    Poll and store the tracks

    GET /api/v1/tasks/:id until completed. Save output.audio_urls or use output.tracks to map the music and no_music files.

    Open
docs/api/music-extractor

API reference

Drop-in code and the full parameter table.

View full reference
curl https://reapi.ai/api/v1/audio/generations \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"audio-music-extractor","audio_url":"https://cdn.example.com/mix.wav","encoder_format":"mp3"}'

Parameter validation failed

Rejected synchronously with the failing field named. Check enum values, ranges, and URL fields — nothing is charged.

Authentication or balance issue

401 means a missing or invalid Bearer key; 402 means the reserve exceeds your balance. Manage keys and credits in the console.

Content or material rejected

Reference material and outputs pass automated moderation. Rejected tasks fail with a clear error and a full refund.

Task failed or timed out

A task that reaches a failed state is never charged — the reserve refunds automatically. Keep the task id and retry when ready.

Frequently asked questions

Common questions about this model.

The music extractor API is an async audio endpoint for extracting the music stem from mixed audio. It is designed for sources where music is mixed with voice or other content. A completed music extractor API task can include both music and no_music outputs for downstream editing.

Related models

Explore more models in the same category.

View all models
start building

Ready to ship?

Try it in the playground or grab an API key to integrate now.

Try music extractionView music extractor docs