> For the complete documentation index, see [llms.txt](https://wiki.gamee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.gamee.com/gameplay/gamee-prizes-faq/how-to-play.md).

# How to play

How to play Prizes

{% hint style="info" %}
*💡Need help finding the answer to your question? Click the 'Search' bar on this Wiki and then choose **Lens** to ask the AI!*
{% endhint %}

You can play GAMEE Prizes on your phone!<br>

**Mobile App**

If you want to enjoy the full experience, you can download our Prizes app on both iOS and Android.  We have many events during the month, so keeping up with the notifications will help you get more chances at winning cash prizes!

Here's the download link for both platforms: [Prizes by GAMEE](https://bit.ly/play-gamee)

**Telegram**

On any chat, just call our bot by tapping "@gamee" and choose from any of our +80 games! Your scores will be shown in the chat conversation and you will be able to compete with your friends in both direct conversations and group chats!


---

# 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://wiki.gamee.com/gameplay/gamee-prizes-faq/how-to-play.md?ask=<question>&goal=<user_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.