Every plan · REST API and MCP
AudioPod's speaker separation API splits a recording into one audio track per speaker: send a file, a URL or a direct upload to POST /api/v1/speaker/extract and poll the job for the tracks. It is the same AudioDiarize engine the dashboard runs, and API access comes with every plan, including free Basic: calls are paid from your prepaid API wallet first, then your credits.
Last updated
At a glance
How it works
FAQ
Yes. POST /api/v1/speaker/extract writes one audio track per speaker, POST /api/v1/speaker/diarize returns the who-spoke-when timeline only, and POST /api/v1/speaker/separate splits 2–4 simultaneous voices. The Python SDK wraps diarize and extract and the Node SDK wraps diarize plus job lookup; neither wraps POST /api/v1/speaker/separate, so call it over REST.
Send num_speakers when you know it, or min_speakers and max_speakers for a range. clustering_threshold (0.3–0.95, default 0.7) fine-tunes detection: lower values find more speakers, higher values fewer.
While the first job is still running and was started less than 3 hours ago, an identical request returns that job with duplicate_of: true and is not charged again. Failed jobs never count as repeats. force_rerun=true submits a new, charged job only when the running one has gone over 30 minutes; a fresher running job is still returned.
Yes. The AudioPod MCP server exposes a separate_speakers tool, so an AI assistant or coding agent can start a separation and fetch the tracks.
Per minute of audio at API prices, not the dashboard's 330 credits per minute: diarization and extraction cost $0.20 per minute from the prepaid API wallet, or 1,500 credits per minute when paid from credits (credits convert at the pay-as-you-go rate). The charge is reserved when the job starts and refunded if it fails. See pricing for plans.