What kind of audio should I send to the voice cleaner API?

Use it for speech-first audio: podcasts, interviews, voiceovers, calls, screen recordings, or user submissions. The voice cleaner API is not a music stem splitter. If you need music extraction, vocal removal, or multistem output, use those dedicated audio pages instead. For music-heavy files, route users to separation instead of cleanup.

How does noise_cancelling_level work?

The voice cleaner API accepts 0, 1, or 2. Start with 1 for normal noisy speech, use 0 when you only need the default cleanup path, and try 2 when the source has stronger background noise. Keep test clips short while choosing the level. Save the chosen value with the task so your team can compare results later.

Can the voice cleaner API reduce echo?

Yes, dereverb_enabled can be turned on when a recording has room echo. Keep it off for sources where the natural room sound matters, because echo reduction can change the character of a voice. The voice cleaner API exposes this as a simple boolean control. Test it on short samples from the same room before using it for a large batch.

How is voice cleaner API pricing calculated?

Jobs are billed per rounded-up source minute. A short test clip bills as one started minute, and longer recordings scale by their rounded duration. See current per-minute rate in the pricing table on this page. Keep your own task record if your backend retries a submission. The voice cleaner API estimator uses the same rounded-minute rule as the docs.

Where is the voice cleaner API reference?

The full docs live at /docs/voice-cleaner. Use POST /api/v1/audio/generations to create the voice cleaner API job and GET /api/v1/tasks/:id to poll for completed output. The docs include the noise level values, dereverb field, output formats, and response shape. Keep the reference open while matching frontend controls to backend validation. The voice cleaner API docs also show which fields can be omitted when defaults are enough.

Voice Cleaner API

Clean noisy speech before publishing or transcription. The voice cleaner API returns clean voice output with optional noise and echo controls.

Input

Source audio*

Drag audio here or click to uploadMP3 / WAV / AAC / OGG · max 20 MB · up to 1 file

MP3 / WAV / AAC / OGG

Noise cancellation0

0, 1, or 2

Splitter

Default auto

Dereverb

Optional

Output format

mp3, wav, flac, aac, or ogg

Result

What you can build with this model

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

podcast speech waveform cleaned for publishing

Voice cleaner API for podcasts and interviews

Use the voice cleaner API before publishing clips, podcasts, field interviews, or webinar recordings. Reduce background noise and return speech that is easier to edit or review. The voice cleaner API is meant for speech-first audio, not music stem splitting. It helps production teams clean uploads before trimming, clipping, captioning, or sending audio to another service. The voice cleaner API also gives user-generated content products a predictable cleanup step before human review.

Clean a voice

Voice cleaner API before transcription

Noisy speech hurts transcripts and review tools. Put the voice cleaner API before your transcription pipeline so the next service receives cleaner voice audio. This is especially useful when uploads come from laptops, meeting rooms, phones, or creator microphones. A cleaner file can make speaker review easier even when the final transcript service stays the same. The voice cleaner API keeps this step async, so long recordings can finish in the background.

Voice cleaner API for user submissions

Screen recordings, support calls, and creator submissions arrive with different rooms and microphones. Run the voice cleaner API as an async prep step before storage or moderation. Your app can keep the original file and attach the cleaned output after polling finishes. That gives reviewers a cleaner version without losing the source file for audit, support disputes, quality checks, comparison, or reprocessing later. Keep both versions available when a customer asks for proof.

Pricing

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

Category	Unit	Price
Voice cleanup
Source speech	1 started minute	$0.2 200 credits

Why reAPI

Why this voice cleaner API stays speech-focused

The voice cleaner API uses the voice cleanup model and keeps the page centered on speech, not music separation. It returns clean voice output for production workflows. That focus makes the playground easier for users who just want noise reduction.

Three noise levels

Set noise_cancelling_level to 0, 1, or 2. That gives product teams a small, clear control instead of exposing a long list of tuning knobs. Start with the middle option in the UI and let advanced users raise or lower cleanup only when they hear a reason. The voice cleaner API keeps this decision small enough for support agents, creators, and reviewers to understand.

Voice cleaner API with the same task shape

Create a task, poll the task id, then download output URLs. The voice cleaner API follows the same contract as the rest of the reAPI async endpoints. Teams can reuse existing queue, retry, and webhook-side storage patterns.

Integrate the voice cleaner API in three steps

step 01
Create an API key
Generate a reAPI key from workspace settings. Use it from your backend to submit speech cleanup jobs.
Open
step 02
Submit a cleanup task
POST model audio-voice-clean with a public audio_url. Add noise_cancelling_level, dereverb_enabled, and encoder_format when needed.
Open
step 03
Poll and download clean speech
GET /api/v1/tasks/:id until completed. Download the clean voice output from output.audio_urls or use output.tracks when labels are present.
Open

View all models

start building

Ready to ship?

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

Try voice cleaning View voice cleaner docs

What you can build with this model

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