> For the complete documentation index, see [llms.txt](https://docs.aavegotchi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aavegotchi.com/gaming/aavegotchi-gaming-console.md). # Aavegotchi Gaming Console The Aavegotchi Gaming Console (AGC) is an onchain layer designed to enhance the gaming experience for users of the Aavegotchi ecosystem. It serves as a platform for storing and sharing granular player and Aavegotchi data across multiple games, enabling developers to craft deep "meta-level" progression and achievement experiences for players, all powered by public onchain data. ## Key Features Key features of the Aavegotchi Gaming Console include: * Overviews of how Aavegotchis and other assets are used within each game * Cross-game player progression * Onchain player Badges * Profile decoration (titles, frames, PFP) ## Interoperabilty FTW Interoperability of assets across various Aavegotchi gaming titles is a key goal of our vision for Aavegotchi gaming. The Aavegotchi Gaming Console acts as the unifying "glue" between all Aavegotchi games, ensuring that developers prioritize interoperability in their game design. Check out all of the associated AGC assets in the [Assets](/gaming/assets.md) section below! --- # 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.aavegotchi.com/gaming/aavegotchi-gaming-console.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.