Workflow

Karaoke Instrumental

Turn any song into a clean karaoke backing track. Soundverse separates the song into stems, drops the vocal stem, and merges everything else into one rendered instrumental.

Quickstart
Request fields
How it works
Results and playback
Pricing

Dedicated route only

This workflow uses POST /v1/karaoke-tracks. It runs a fixed multi-step pipeline; there is no generic tool_id for it.

Quickstart

POST/v1/karaoke-trackskaraoke instrumental

curl -X POST https://apiv2.soundverse.ai/v1/karaoke-tracks \
  -H "Authorization: Bearer sksoundverse_..." \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: karaoke-track-001" \
  -d '{
  "song_file_id": "018f0000-0000-7000-8000-000000000002",
  "license": "royalty_free"
}'

The song_file_id must be an active uploaded audio file owned by the authenticated enterprise account.

Getting a song_file_id

Upload the file first via POST /v1/files — either {"source_url": "..."} if you already host it, or a multipart/form-data file part to upload bytes directly. Both return a file_id owned by your account, ready to pass here.

Request fields

Field	Type	Required	Default	Description
song_file_id	uuid	Yes	—	ID of the song to make a karaoke backing track from, an audio file owned by the authenticated enterprise account (upload it first via POST /v1/files). Maximum 60 MiB.
license	license tier	No	"royalty_free"	License tier to price and attach to every step of the pipeline.

How it works

Each request runs 3 steps in order:

Separating the song into its individual stems.
Merging all instrumental stems (no vocals) into the karaoke backing track.
Rendering the karaoke instrumental into one playable file.

Progress streams over GET /v1/generations/{task_id}/stream as each step starts and finishes.

Results and playback

Poll GET /v1/generations/{task_id} until the task is completed. The finished result is added to the authenticated account’s Soundverse Library. Enterprise API outputs are hidden from public/profile surfaces by default.

For API-only download, resolve the output’s file_id with GET /v1/files/{file_id}/url and use the returned short-lived signed URL.

Pricing

This workflow is priced pass-through: you are billed for each step the pipeline runs, at that step’s enterprise rate, in the license tier you requested. The pipeline itself adds no separate fee, and your billing ledger shows one entry per step. The steps that carry the cost are:

Stem separation
Mixing
Final render

There is no fixed per-request price; the total depends on the input and on which optional steps run.

← Similar BeatDrumless Practice Mix →