> For the complete documentation index, see [llms.txt](https://sharpai.gitbook.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sharpai.gitbook.io/documentation/sharpai-legacy.md). # Sharpai Legacy Welcome to the world of Sharpai Legacy! Fasten your seatbelts and get ready to embark on an exhilarating adventure that will take you through the thrilling universe of blockchain gaming! Sharpai Legacy is a one-of-a-kind onchain game built on the **Arbitrum** network, designed to push your strategic and competitive skills to the limit. Think of it as a high-octane race through cyberspace where anyone can emerge victorious and claim the spoils! This is not your typical blockchain game; Sharpai Legacy doesn't feature any tokens, but rather, an enthralling collection of NFTs that players can earn or trade as they navigate this captivating landscape. With a defined beginning and end, Sharpai Legacy offers you the unique opportunity to experience the thrill of the chase while you compete against others to win the ultimate reward. Don't worry if you're not the fastest racer, though – fortune favors the bold, and Lady Luck might just smile upon you with some delightful surprises along the way! Are you ready to dive into the exhilarating world of Sharpai Legacy and unravel its mysteries? Just keep reading, and let the games begin! --- # 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://sharpai.gitbook.io/documentation/sharpai-legacy.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.