> For the complete documentation index, see [llms.txt](https://docs.gpubase.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gpubase.network/readme.md). # Overview Welcome to the GPUBase Network documentation! This guide will provide you with everything you need to know about our decentralized platform, designed to make high-performance GPU computing accessible, secure, and efficient. GPUBase Network connects users needing computational power with GPU providers worldwide, leveraging blockchain technology to create a transparent and reliable ecosystem. Our platform offers a unique combination of features, including seamless GPU integration through the Provider App, smart contract-based transactions for maximum security, and a well-structured token economy that supports network sustainability and user rewards. In this documentation, you’ll learn how GPUBase Network works, how to get started, and the benefits of being part of our growing community. Join us on this journey to revolutionize decentralized computing! --- # 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.gpubase.network/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 `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.