> For the complete documentation index, see [llms.txt](https://docs.cresta.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cresta.com/cresta-support/submit-documentation-request.md).
# Submit Feedback on Articles
Submit feedback and tell us what would help you complete your task.
Use the feedback option available on every article page to share your experience and help improve the documentation. Use the **Feedback** option in Cresta Help to:
* Provide feedback about the documentation.
* Request new documentation.
* Report errors or inaccuracies.
* Suggest improvements to existing content.
Locate the **Was this helpful?** section on the right side of the article, below the table of contents.
To submit feedback:
1. Click the emoji that best reflects your experience.
2. Enter your feedback in the text box.
3. Click **Submit**.
If the content was helpful, share what worked well. If the content was unclear or incomplete, describe what was missing or how it can be improved.
This input helps ensure the documentation stays accurate and useful.
{% hint style="danger" icon="bullhorn" %}
**Cresta Help does not have a separate documentation request portal.**
To request new documentation, use the **Feedback** option, enter the details of your documentation request and **Submit**.\
The documentation team reviews all submitted requests and feedback to help prioritize future content updates.
{% endhint %}
---
# 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.cresta.com/cresta-support/submit-documentation-request.md?ask=&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.
