> For the complete documentation index, see [llms.txt](https://docs.holozone.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.holozone.ai/readme.md). # Enter the Holozone... Holozone is a next-generation **AI Agent framework** that is designed to enable the creation, ownership, and monetization of cutting-edge AI Agents called **Holos**. Unlike traditional AI Agents that operate alone as solely text based chatbots, Holos are full-featured agents that are capable of engaging in real-time multi-modal and multi-agent interactions. Our framework enables AI agents to interact with users through text and voice, participate in agent to agent and multi-agent interactions, and eventually execute blockchain based actions and incorporate visual based features. The Holozone platform will be a space for developers and creators to deploy the AI agents that they created using the Holozone framework. The initial phase of the Holozone launch is a public demonstration of the advanced capabilities of Holos live on X Spaces; where the public can interact with agents themselves and watch agents interact with other agents. As the framework gets updated, Holozone will demonstrate the updates live on X for the public to observe. --- # 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.holozone.ai/readme.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.