> For the complete documentation index, see [llms.txt](https://docs.algenta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.algenta.ai/help.md). # Help - [Troubleshooting](https://docs.algenta.ai/help/troubleshooting.md): Hit a snag? Find your message, copy the fix, get back to work — most Algenta issues are a missing key, an engine it can't reach, or a license flag. - [Glossary](https://docs.algenta.ai/help/glossary.md): Every Algenta term in one place — the engine, the surfaces, decision planning, governed data, agentic runs, deployment, and licensing vocabulary, each defined once. - [Quick reference](https://docs.algenta.ai/help/quick-reference.md): One-page cheat sheet — every common Algenta task mapped to its HTTP endpoint, de CLI command, and Python SDK call, plus the handful of env vars you need most. - [Using these docs with AI](https://docs.algenta.ai/help/ai-access.md): Use the Algenta docs with any AI — the auto-generated llms.txt context files, per-page Markdown, the built-in MCP server, and copy/open-in-chat actions. - [Changelog](https://docs.algenta.ai/help/changelog.md): What's new in Algenta — notable releases, improvements, and fixes to the engine, SDKs, MCP server, and self-hosted deployment, newest first. --- # 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.algenta.ai/help.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.