> 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/help-center/readme.md).

# Podigee Help Center

Find quick answers, resolve common problems, and contact Podigee Support.

Use the Help Center when you have a question or when something does not work as expected. The Help Center covers Podigee hosting questions and AI agent questions.

## Find a solution

1. Search for the task, setting, or error message.
2. Follow the steps in the article.
3. Check the expected result.
4. Contact Podigee Support if the problem continues.

## Resolve a hosting question

Use the Podigee hosting section for quick answers about your account, your subscription, uploads, feeds, imports, team seats, analytics, and Content Hub. Each answer names the place in Podigee where you act and the Documentation page that describes the complete procedure.

## Resolve an AI agent problem

Use the AI agents section for connection, authorization, upload, publication, import, analytics, distribution, and private-feed recovery. Start with the article that matches the failed step. Each article tells you what sanitized evidence to keep if you need Podigee Support.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.podigee.com/help-center/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.