> For the complete documentation index, see [llms.txt](https://crypto-bike.gitbook.io/crypto-bike.game/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://crypto-bike.gitbook.io/crypto-bike.game/gameplay/type-of-races.md).
# TYPE OF RACES
## SIMPLE MODE
The type of race where the player can choose the number of opponents to face. Races with 1, 3, and 5 participants are available. Races are organized, considering the players' level and rank. The reward is in MTCB tokens.
## PVP
In PVP races, players compete for one on one within their rank.
Two types of races are available in PvP mode:
* The Death Race involves the player betting on his bike and all its items and components. Upon winning, the winner receives the opponent's bike as a reward.
* MTCB Race - involves the player placing a bet on their bike to win in MTCB tokens. When a player wins, they receive their opponent's bet. The amount of bet depends on the rank of the bike.
## TOURNAMENT
Players must purchase an entry ticket to participate in the Classic Tournament. The initial stage includes qualifying rounds where players are matched based on bike characteristics for a more balanced competition.
Each tournament round consists of 4 racers, with only two advancing to the next round. The players generate the prize pool, with 60% allocated for prizes and 40% for ecosystem support and additional rewards.
The number of participants can range from 16 to 1600, and the tournament is held weekly. Users can track their progress in the tournament through the leaderboard. The game offers three prize-winning positions.
## TVT
TVT (Team versus Team) is a team-based racing mode. Players can create teams consisting of two or three participants.(TBA)\
---
# 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 following URL with the `ask` and `goal` query parameters:
```
GET https://crypto-bike.gitbook.io/crypto-bike.game/gameplay/type-of-races.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 `build a script that syncs our docs to a CMS` 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.
