Workflow
Similar Beat
Keep the vocals of a rap track exactly as they are and replace the beat underneath with a new, similar one. Soundverse splits the track, generates a brand-new instrumental in your requested style at the original tempo and key, and lays the untouched original vocal back over it.
Dedicated route only
This workflow uses POST /v1/beat-swaps. It runs a fixed multi-step pipeline; there is no generic tool_id for it.
Quickstart
POST/v1/beat-swapssimilar beat
curl -X POST https://apiv2.soundverse.ai/v1/beat-swaps \
-H "Authorization: Bearer sksoundverse_..." \
-H "Content-Type: application/json" \
-H "Idempotency-Key: beat-swap-001" \
-d '{
"song_file_id": "018f0000-0000-7000-8000-000000000002",
"beat_style": "dark trap, heavy 808s, sparse piano",
"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 rap track whose beat should be replaced, an audio file owned by the authenticated enterprise account (upload it first via POST /v1/files). Maximum 60 MiB. |
| beat_style | string | Yes | — | What the new beat should sound like: genre, mood, and instrumentation (e.g. 'dark trap, heavy 808s, sparse piano'). The original instrumental is used as the style reference on top of this, and the new beat is generated at the original track's detected BPM and key so the untouched rap still sits in time over it. |
| license | license tier | No | "royalty_free" | License tier to price and attach to every step of the pipeline. |
How it works
Each request runs 6 steps in order:
- Splitting the rap into its acapella and its original beat.
- Detecting the original track’s BPM and key.
- Generating the new beat in the requested style at the original BPM and key.
- Trimming the new beat to the length of the original rap.
- Laying the original rap over the new beat.
- Rendering the finished beat swap into one playable file.
Progress streams over GET /v1/generations/{task_id}/stream as each step starts and finishes.
Notes
The new beat is generated at your track’s detected tempo and key and trimmed to the length of the original vocal, and the original vocal is then laid over it.
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
- Tempo and key detection
- Instrumental generation (similar music)
- Duration trim
- Mixing
- Final render
There is no fixed per-request price; the total depends on the input and on which optional steps run.