> For the complete documentation index, see [llms.txt](https://docs.splinterlands.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.splinterlands.com/rewards/leaderboard-rewards.md).
# Leaderboard Rewards
Players may compete for spots on the Modern and Wild Champion Leaderboards. Players may choose to compete for spots in one format or both. The top 50 spots pay out between 20,000 and 200,000 DEC at the end of each season. This means that a player can get high up the leaderboards for each and get two season prizes as a result, one for **Modern** and one for **Wild**.
### **Tie Breaks**
In case of a Rating tie, the following rules will be applied as tie-breakers, in order of precedence:
1. The player with the highest win ratio **(WINS/BATTLES)** this season wins the tie.
2. The player with the highest **MAX STREAK** this season wins the tie.
3. If still tied, the player with the most **WINS** this season wins the tie.
---
# 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://docs.splinterlands.com/rewards/leaderboard-rewards.md?ask=&goal=
```
`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.