> For the complete documentation index, see [llms.txt](https://docs.kusatech.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kusatech.io/terms-and-conditions.md). # Terms and Conditions Welcome to our project, where your journey begins. We appreciate your interest and encourage a thorough exploration of this whitepaper before immersing yourself in the exciting realms of our platform or engaging with the $KUSA token. The terms and conditions articulated here form the bedrock of a seamless, responsible, and compliant experience on our platform. By partaking in activities such as buying, selling, trading, transferring, depositing, or withdrawing $KUSA tokens, you affirm not only a complete grasp of the outlined terms but also your eligibility for cryptocurrency transactions and participation in gambling products in your jurisdiction. This commitment extends to ensuring the legality and permissibility of product usage in your specific country and region. Embracing this agreement is pivotal for a journey that is not just technologically innovative but also responsibly navigated in accordance with legal standards. --- # 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.kusatech.io/terms-and-conditions.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.