> For the complete documentation index, see [llms.txt](https://toms-whitepaper.gitbook.io/tomclicker-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://toms-whitepaper.gitbook.io/tomclicker-whitepaper/game-tom-clicker/usdtom-airdrop.md).

# $TOM AIRDROP

Exactly: Have fun and make money.&#x20;

The $TOM Airdrop feature at the end of each season represents a very important moment in the game, as players are rewarded after days of competition.

### 🛩️ Airdrop Mechanics:

* **Rank-Based Distribution:** The number of $TOM tokens you receive is directly tied to your final ranking. The higher your position on the leaderboard, the larger your share of the airdrop.&#x20;
* We will try to share as much Airdrop as possible and to as many players as possible, as long as they fulfil the minimum requirements.
* Each season will last for a set number of days, and the end of each season will be announced a few days in advance

$TOM token ≠ TOM Point

There is no specific ratio between TOM Points and $TOM Tokens. TOM Points are used to rank you in the game, and depending on your position, you will receive more or less Airdrop in the form of $TOM. This means that a player with 10M TOM Points will always receive more $TOM than a player with 9M TOM Points.


---

# 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://toms-whitepaper.gitbook.io/tomclicker-whitepaper/game-tom-clicker/usdtom-airdrop.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.
