Is there a Zapier integration?

Not yet — in progress. We're building Zapier, Make, Pipedream, and n8n listings via a shared OAuth + actions surface. Email partners@audiopod.ai to get notified at launch.

What's available today via the REST API?

The full studio — voice cloning, music and rap generation, transcription in 100+ languages, audiobook production, stem separation, denoise, podcast tooling. OAuth 2.0 and API keys. Full reference at docs.audiopod.ai.

How does the MCP server work?

AudioPod publishes a Model Context Protocol server so AI agents (Claude, Cursor, and any MCP-aware client) can call AudioPod tools natively. See /for-agents for setup and the manifest.

Can I subscribe to webhooks?

Yes. Subscribe to job-completion events from your dashboard to get notified when long-running generations land. Webhook payloads are HMAC-signed for verification.

How do I get listed as a partner?

Platform launches are joint engineering projects. Email partners@audiopod.ai with the subject "Integration partnership" and we'll come back with next steps.

Integrations

AudioPod, in whatever stack you ship from.

Three integration surfaces are live today — a REST API, an MCP server, and webhooks. App-directory listings for Zapier, Make, Pipedream, and n8n are in progress.

API documentation

🎧 Listen to this page

At a glance

How AudioPod plugs into your stack.

Three live surfaces today (REST · MCP · webhooks) feeding the same studio engine and fanning out to your downstream pipeline.

REST API
MCP Server
Webhooks

AudioPod

Audio file
Dashboard
Agent response

Live today

Three surfaces you can wire up this afternoon.

Live

REST API

The whole studio behind a clean HTTP API. Voice, music, transcription, separation, denoise, audiobook — same endpoints the dashboard uses. OAuth + API keys.

Read the docs

Live

MCP server

An MCP server so AI agents can talk to AudioPod natively — same studio, agent-callable. Used by Claude, Cursor, and any MCP-aware client.

See agent surface

Live

Webhooks

Subscribe to job-completion events from your dashboard. Get notified when long-running generations land, route results into your downstream pipeline.

Set up webhooks

Coming soon

Where we're showing up next.

Listings in the major no-code / low-code app directories. If one of these is blocking you today, email partners@ and we'll prioritize.

Coming soon

Zapier

Triggers (job completed, voice created) and actions (generate TTS, run transcription, denoise) inside the Zapier app directory. Currently in development.

Coming soon

Make

Same trigger / action surface in the Make app catalog. Targets Make-native users who already wire audio workflows there.

Coming soon

Pipedream

Components package in the Pipedream registry. Built for the developer-leaning automation crowd.

Coming soon

n8n

Self-hosted-friendly automation. AudioPod community node, contributable on the n8n marketplace.

How AudioPod fits

Three patterns we see most.

Workflow automation

Zapier / Make / n8n flows that trigger TTS, transcription, or denoise as a step inside a larger pipeline (notion → audio narrator, support inbox → cleanup → archive).

Agent toolchains

AI agents calling AudioPod via MCP to make or transform audio inside larger reasoning loops. Same studio that Claude reaches via MCP, you reach via REST.

In-product features

SaaS products embedding AudioPod TTS, transcription, or audio cleanup inside their own UX, billed against an enterprise plan.

Partner with us

Want AudioPod inside your product?

Want to integrate AudioPod into your product?

If you'd like to ship an AudioPod-powered audio feature inside your own app — or list AudioPod inside your platform's app directory — email partners@. We treat platform launches as joint projects, with engineering on both sides.

Email partnerships

Common questions

Integrations FAQ

Read the docs. Or write to us.

If the live surfaces cover you, jump straight to the docs. If you need something custom, partners@ is the fastest path.

API docs

Integrations

AudioPod, in whatever stack you ship from.

Three integration surfaces are live today — a REST API, an MCP server, and webhooks. App-directory listings for Zapier, Make, Pipedream, and n8n are in progress.

API documentation

🎧 Listen to this page

At a glance

How AudioPod plugs into your stack.

Three live surfaces today (REST · MCP · webhooks) feeding the same studio engine and fanning out to your downstream pipeline.

REST API
MCP Server
Webhooks

AudioPod

Audio file
Dashboard
Agent response

Live today

Three surfaces you can wire up this afternoon.

Live

REST API

The whole studio behind a clean HTTP API. Voice, music, transcription, separation, denoise, audiobook — same endpoints the dashboard uses. OAuth + API keys.

Read the docs

Live

MCP server

An MCP server so AI agents can talk to AudioPod natively — same studio, agent-callable. Used by Claude, Cursor, and any MCP-aware client.

See agent surface

Live

Webhooks

Subscribe to job-completion events from your dashboard. Get notified when long-running generations land, route results into your downstream pipeline.

Set up webhooks

Coming soon

Where we're showing up next.

Listings in the major no-code / low-code app directories. If one of these is blocking you today, email partners@ and we'll prioritize.

Coming soon

Zapier

Triggers (job completed, voice created) and actions (generate TTS, run transcription, denoise) inside the Zapier app directory. Currently in development.

Coming soon

Make

Same trigger / action surface in the Make app catalog. Targets Make-native users who already wire audio workflows there.

Coming soon

Pipedream

Components package in the Pipedream registry. Built for the developer-leaning automation crowd.

Coming soon

n8n

Self-hosted-friendly automation. AudioPod community node, contributable on the n8n marketplace.

How AudioPod fits

Three patterns we see most.

Workflow automation

Zapier / Make / n8n flows that trigger TTS, transcription, or denoise as a step inside a larger pipeline (notion → audio narrator, support inbox → cleanup → archive).

Agent toolchains

AI agents calling AudioPod via MCP to make or transform audio inside larger reasoning loops. Same studio that Claude reaches via MCP, you reach via REST.

In-product features

SaaS products embedding AudioPod TTS, transcription, or audio cleanup inside their own UX, billed against an enterprise plan.

Partner with us

Want AudioPod inside your product?

Want to integrate AudioPod into your product?

Email partnerships

Common questions

Integrations FAQ

Read the docs. Or write to us.

If the live surfaces cover you, jump straight to the docs. If you need something custom, partners@ is the fastest path.

API docs