# Definitions

* **Client App** *Your Client or your Mobile App.*
* **Client Server** *You App Server*
* **Game Client** *Game-Ox's Game.*
* **Game Server** *Game-Ox's Server*
* **User Token** *User Authentication API Token (Bearer, JWT..)*

### Scenario in short overview:

&#x20;

1- **Client App** open The **Game Client** Through a URL Provided by Game-ox.

2- **Client App** passes the required parameters to the **Game Client** URL.

3- **Game Client** passes the parameters sent by the app to the **Game Server**.

4- **Game Server** passes the required parameters to the **App Server** to get latest user info.

5- **Game Server** updates User Information received from the **App Server**

6- **Game Server** increase, decrease user coins through the App Server according the the **Game  Client** reactions.

<figure><img src="https://2011923766-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNjtcFMSBH03sFy2zsnIe%2Fuploads%2FmgoywbKi9LJ41RmSLBEm%2FMy%20First%20Board.jpg?alt=media&#x26;token=dcc78631-f9c7-4d93-a5a1-2b3ef8e1554b" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://docs.game-ox.com/documentation/definitions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
