> 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/others/about-us.md).

# About Us

Avery Games is a pioneering Web3 gaming platform that emphasizes true ownership of digital assets through blockchain technology. Players can own, trade, and sell in-game assets independently, fostering a player-driven economy. Avery Games also supports interoperability across multiple titles, allowing users to use assets in different games within the ecosystem. With community feedback and governance mechanisms via the $AVERY token, players have a say in game development, creating a dynamic, player-focused gaming environment.

[Website ](https://www.averygames.com/)| [X ](https://x.com/AveryGames_offc)| [Telegram ](https://t.me/averygames_official_chat)


---

# 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/others/about-us.md?ask=<question>&goal=<endgoal>
```

`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.