New: 13 caption styles
Developers

Jellypod developer resources

Build with Jellypod podcasts, videos, shorts, and voiceovers. Find the REST API reference, OpenAPI specification, MCP server, and guides for AI agents.

Jellypod MCP server

Let an AI assistant create in Jellypod for you. The remote Model Context Protocol server at https://mcp.jellypod.com/mcp runs podcast workflows and generates videos and shorts. Clients connect over Streamable HTTP with OAuth 2.1 through Jellypod sign-in, or with an API key as a bearer token.

Machine-readable site content

Plain-text versions of the site for LLMs and retrieval systems. Append .md to any docs URL to get it as markdown.

Frequently asked questions

What is the Jellypod API?
The Jellypod API is a REST API at https://api.jellypod.com. Create and publish podcast episodes, manage hosts and sources, browse voices, and read analytics. Separate video, short, and voiceover endpoints let you create media, check status, retry failed generation, and retrieve downloads. The reference is at https://www.jellypod.com/docs/api, with an OpenAPI 3.1 specification at https://www.jellypod.com/openapi.json.
How do I authenticate with the Jellypod API?
Create an API key in the Jellypod studio under Developers, then API Keys, and send it as an Authorization: Bearer header. API keys require the Creator plan or higher. Generation through the API uses the same credits as the studio.
What is the Jellypod MCP server?
The Jellypod MCP server is a remote Model Context Protocol server at https://mcp.jellypod.com/mcp. A connected assistant can manage podcasts and generate episodes, videos, and shorts on your account. Connection methods and inline playback depend on your client.
Can I use local files as sources?
Yes, through the API. Request a source upload, send the file to the returned upload URL, and complete the upload. Wait for processing to finish before using documents or images for a voiceover. The MCP server does not accept files, so use the studio or the API when Jellypod needs the original.
What do API errors look like?
Every non-2xx response is an RFC 9457 application/problem+json document with a machine-readable type, a title, the HTTP status, a request_id for support, and per-field validation errors when relevant.

Start creating with Jellypod today

Turn any idea, document, or link into editable, high-quality podcasts and videos. Reach global audiences in your own voice, in 121 languages.