> For the complete documentation index, see [llms.txt](https://docs.pancakeswap.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pancakeswap.finance/play/prediction/prediction-leaderboard.md).
# Prediction - Leaderboard
The **Prediction Leaderboard** highlights the top participants in PancakeSwap Prediction.\
It allows players to see how they rank against others based on different metrics.
> **Note**: A wallet must participate in at least **10 rounds** to appear on the leaderboard by default.\
> Specific wallet addresses can still be searched manually.
### How to Use the Leaderboard
1. **Access the Leaderboard** directly from the Prediction page.
2. **Filter by Token**
* Choose the market (BNB, BTC, ETH) you want to view top players for.
3. **Sort by Ranking Criteria**
* **Rounds Played**: Total number of rounds a user has participated in.
* **Net Winnings**: Total tokens won from successful predictions, after the 3% fee is deducted.
* **Total BNB**: Aggregate amount of BNB used for predictions.
* **Win Rate**: Ratio of rounds won to total rounds participated.
4. **Search by Wallet Address**
* Enter a wallet address to display its scorecard, even if it does not meet the 10-round threshold.
***
---
# 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://docs.pancakeswap.finance/play/prediction/prediction-leaderboard.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 `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.
