> For the complete documentation index, see [llms.txt](https://averygames.gitbook.io/avery/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://averygames.gitbook.io/avery/game-details/avery-games.md). # Avery Games Avery Games is designed to be an expansive ecosystem of interconnected games, each contributing to the broader mission of empowering players through true asset ownership and decentralized economies. The first title, *Avery Sword*, will set the foundation by introducing the core principles of the ecosystem—leveraging Web3 technology to grant players ownership of in-game assets and the ability to trade them freely. Following this, *Avery Race* and additional titles will be developed, each offering unique gameplay experiences but operating within the same ecosystem. A key feature of this ecosystem is the $AVERY token, which will serve as the universal currency across all games. This integration allows players to use the same token for in-game purchases, asset trading, staking, and other financial activities, creating a seamless economic environment. The $AVERY token not only enhances the player experience by providing real-world value to in-game achievements but also strengthens the connection between the different games. Players can accumulate assets and rewards in one game and utilize them in another, fostering a more dynamic and immersive gaming experience across the entire Avery Games ecosystem. By offering multiple titles under one ecosystem and utilizing a common token, Avery Games aims to build a thriving community where players can engage with different game genres while retaining ownership and value continuity. This approach aligns with the vision of transforming the traditional gaming model, where player assets are often locked within individual games, and paves the way for a more inclusive and player-driven gaming future. --- # 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://averygames.gitbook.io/avery/game-details/avery-games.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.