> For the complete documentation index, see [llms.txt](https://docs.podigee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podigee.com/readme.md). # Podigee documentation Find the part of the Podigee documentation that matches your goal, your role, and your interface. This site contains the documentation for Podigee. Use this page to find the correct area for your goal. Then use the navigation of that area to find the page that you need. ## Start with your goal | Your goal | Go to | | ---------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------- | | You are new to Podigee and want to publish your first episode. | [Start here](https://docs.podigee.com/documentation/start-here/start-here) | | You want to complete a task, for example edit a podcast, distribute a show, or read analytics. | [Documentation](https://docs.podigee.com/documentation) | | You have a question, or something does not work as expected. | [Help Center](https://docs.podigee.com/help-center) | | You want to connect an AI application, such as Claude or ChatGPT, to Podigee through the Model Context Protocol (MCP). | [AI Agents and MCP](https://docs.podigee.com/documentation/start-here/ai-agents) | | You build your own software integration with the Podigee application programming interface (API). | [REST API](https://docs.podigee.com/api-reference/rest-api) | | You want to know what changed in Podigee. | [Changelog](https://docs.podigee.com/changelog) | ## Areas of this site Use the site header to switch between the areas. | Area | Content | | ------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [Documentation](https://docs.podigee.com/documentation) | Instructions and explanations for the product areas, for example podcasts and episodes, publishing, analytics, and account administration. Each area starts with the simple path. Advanced options follow. | | [Help Center](https://docs.podigee.com/help-center) | Short answers to frequent questions, and solutions for common problems. | | [API Reference](https://docs.podigee.com/api-reference) | Technical reference for developers who connect software to Podigee. | | [Changelog](https://docs.podigee.com/changelog) | Product changes that affect your work. | ## Find the tab for your interface Podigee has two interfaces for the same account: the **classic view** and the **Podigee workspace**. Both use the same podcasts, episodes, and account data. Only the click paths and the labels are different. * A page with steps shows one tab for each interface. Select the tab of the interface that you use. * If the account menu contains **Switch to classic view**, you use the Podigee workspace. Otherwise, you use the classic view. The account menu of the classic view can contain **Switch to new view**. * If a job is not available in the Podigee workspace yet, the workspace tab tells you. Use the classic view for that job. | To learn | Read | | ---------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | How to switch between the two interfaces | [Choose between the classic view and the Podigee workspace](https://docs.podigee.com/documentation/start-here/start-here/choose-between-the-classic-view-and-the-podigee-workspace) | | How each page marks its interface | [Which interface a page describes](https://docs.podigee.com/documentation/start-here/start-here/which-interface-a-page-describes) | ## Read a task page Each task page helps you complete one job. The sections always come in the same order: 1. **Before you start** lists the conditions, for example the role or the plan that you need. 2. The steps tell you what to do. Each step gives one instruction. 3. **Expected result** tells you what you see when the task is complete. 4. **If you cannot complete the task** lists the causes of frequent problems and a safe recovery. 5. **Next step** links to the task that usually follows. Pages with a title that starts with **Understand** explain a concept. Reference pages list exact values, such as fields, limits, and error codes. ## Get help If the documentation does not answer your question, read [Find help and contact Podigee Support](https://docs.podigee.com/documentation/start-here/start-here/find-help-and-contact-support). That page tells you what to prepare before you contact Podigee Support. ## Use this documentation with an AI agent * Each page is also available as Markdown. Add `.md` to the URL of the page. * The file [llms.txt](https://docs.podigee.com/llms.txt) lists all pages with a short description. * Tell your agent to read [Which interface a page describes](https://docs.podigee.com/documentation/start-here/start-here/which-interface-a-page-describes) first. The agent can then select the pages by their `surfaces` value. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.podigee.com/readme.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.