Developers

Jellypod Developer Resources

Everything developers and AI agents need to build on Jellypod: the REST API reference, OpenAPI specification, API key authentication, the remote MCP server, and agent skills.

Jellypod API

A REST API at https://api.jellypod.com for podcasts, episodes, hosts, sources, voices, and analytics. Authenticate with an API key sent as a bearer token. Every error is an RFC 9457 application/problem+json response.

Jellypod MCP server

A remote Model Context Protocol server at https://mcp.jellypod.com/mcp (Streamable HTTP). Clients authenticate with OAuth 2.1 through Jellypod sign-in, or with an API key as a bearer token.

Agent skills and instructions

Skills teach AI coding agents how to call the Jellypod API correctly. Install them with npx skills add Jellypod-Inc/skills.

  • Jellypod skills on GitHub

    Public repository with SKILL.md files for the Jellypod API, plus agent setup instructions.

  • Skills catalog

    Catalog of Jellypod skills and plugins for Claude Code and other agents.

Machine-readable site content

Text versions of the site for LLMs and retrieval systems. Any docs page also serves markdown by appending .md to its URL.

Frequently asked questions

What is the Jellypod API?
The Jellypod API is a REST API at https://api.jellypod.com that lets developers create podcasts, hosts, and sources, generate and publish episodes, browse voices, and read analytics. It is documented 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. Generating episodes 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. It uses Streamable HTTP transport and OAuth 2.1, so Claude, ChatGPT, Cursor, and other MCP clients can create and publish podcasts on your account from a chat.
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.

Ready to create your podcast?

Go from idea to published episode in minutes. No recording, editing, or experience required.

Pricing on your terms

Pick the plan that works best for you

Pricing details

Start Podcasting

Publish your first episode in minutes

Open the Studio