> For the complete documentation index, see [llms.txt](https://docs.zbrain.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zbrain.ai/zbrain-documentation.md). # ZBrain Documentation ZBrain documentation offers clear, structured support for deploying AI Agents across business functions with ease and precision. #### Welcome to the ZBrain Builder documentation! This documentation serves as the central reference for understanding ZBrain Builder, a platform designed for enterprise AI development. It offers structured guidance on the platform’s core features, including building and managing knowledge bases, automating workflows with Flows, creating Agents for autonomous task execution, and configuring Prompts to enhance AI performance. With a focus on practical tutorials, this resource provides step-by-step instructions and interactive examples to help you create AI applications and manage scalable, enterprise-ready AI solutions. The documentation also includes detailed API references and covers best practices for integrating data sources, automating tasks, and monitoring system performance. --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://docs.zbrain.ai/zbrain-documentation.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 `build a script that syncs our docs to a CMS` 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.