> For the complete documentation index, see [llms.txt](https://docs.gremsy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gremsy.com/payloads/general.md).
# GENERAL
Welcome to the Gremsy Payload Support page, your one-stop destination for expert assistance with Gremsy's cutting-edge payload solutions. Whether you’re integrating our advanced payload systems into your projects or need troubleshooting guidance, our dedicated support team is here to ensure optimal performance and seamless operation.
On this page, you’ll find detailed product manuals, firmware updates, and FAQs tailored to address common inquiries. For personalized support, connect with our support team via `support@gremsy.com` who can provide step-by-step assistance, helping you get the most out of your Gremsy products. We're committed to your success and are here to support you every step of the way.
***
---
# 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.gremsy.com/payloads/general.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.
.png?alt=media&token=6cd4f4d5-b051-48f0-b28c-03fd6118bd53){kind=link}