> 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/documentation/start-here/start-here/which-interface-a-page-describes.md). # Which interface a page describes How the documentation marks which Podigee interface a page describes, for readers and for AI agents. Use this page to read the documentation correctly when you, or an AI agent that works for you, use one of the two Podigee interfaces. ## Two interfaces, one backend Podigee has two customer interfaces: * The **classic view** is the full set of settings and tools. * The **Podigee workspace** is the new interface for podcasts, episodes, publishing, analytics, and Podigee AI. Both interfaces work on the same backend. Plan limits, permissions, the REST API, the MCP server, and the `pdg` CLI behave the same behind both. Only the click paths and the labels differ. To switch, see the page [Choose between the classic view and the Podigee workspace](/documentation/start-here/start-here/choose-between-the-classic-view-and-the-podigee-workspace.md). ## The surfaces label Every page carries a `surfaces` value in its metadata. The same value is in the page record of the content catalog that ships with the documentation source. | Value | The page describes | | ------------------- | ----------------------------------------------------------------------------------------- | | `classic_view` | Steps and labels of the classic view | | `podigee_workspace` | Steps and labels of the Podigee workspace | | `mcp` | The MCP server, the connectors, and the `pdg` CLI, which are the same for both interfaces | | `rest_api` | The REST API, which is the same for both interfaces | | `any` | A concept, a limit, or a reference that does not depend on the interface | A page with both `classic_view` and `podigee_workspace` shows the procedure of each interface in its own tab, **Classic view** and **Podigee workspace**. The parts outside the tabs apply to both. A page with only `classic_view` says in the workspace tab that the workspace does not include the job yet. ## How an AI agent should read the documentation 1. Read this page and the switch page first. 2. Find out which interface the person uses. The account menu shows **Switch to new view** in the classic view and **Switch to classic view** in the Podigee workspace. 3. Use the steps of the matching tab. The parts outside the tabs apply to both interfaces. 4. Treat limits, plan gates, API contracts, and MCP tools as valid for both interfaces. 5. Do not guess a workspace click path for a job that the documentation marks as not included yet. Use the classic view or the MCP tools for that job. ![The open account menu on a podcast page of the classic view with the item Switch to new view](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-0abe1451181b64151f8b4be73aa74473d761458b%2Fdoc-start-009-classic-account-menu.png?alt=media) In the classic view, the account menu shows Switch to new view; this identifies the interface. ## Coverage by area | Area | Both interfaces | Classic view only | Concept, reference, or API | | ----------------------------------------------------------------------------------------------- | --------------- | ----------------- | -------------------------- | | [Start here](/documentation/start-here/start-here.md) | 4 | 0 | 3 | | [Hosting and podcast management](/documentation/create-and-publish/hosting-and-management.md) | 8 | 6 | 0 | | [Episode production](/documentation/create-and-publish/production.md) | 8 | 12 | 0 | | [Publishing and distribution](/documentation/create-and-publish/publishing-and-distribution.md) | 7 | 6 | 1 | | [Analytics](/documentation/grow-and-monetize/analytics.md) | 8 | 1 | 2 | | [Integrations](/documentation/connect-and-administer/integrations.md) | 0 | 3 | 10 | | [Account and team administration](/documentation/connect-and-administer/account-and-team.md) | 1 | 9 | 2 | | [Troubleshooting](/documentation/connect-and-administer/troubleshooting.md) | 4 | 4 | 0 | The [AI Agents and MCP](/documentation/start-here/ai-agents.md) pages and the REST API pages apply to both interfaces without change. --- # 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/documentation/start-here/start-here/which-interface-a-page-describes.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.