> For the complete documentation index, see [llms.txt](https://planetary-defense-guide.gitbook.io/guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://planetary-defense-guide.gitbook.io/guide/web-game/leaderboard.md).
# Leaderboard
## **Can a game like this really be without a leaderboard?**
The leaderboard displays the rankings of the most active users. The rankings are divided into:
* **Top Grinders:** highest number of claims made on missions
* **Top TLM:** highest number of TLMs extracted from the missions
* **Top DEF:** highest number of DEFs extracted from the missions
* **Top Chests:** highest number of Quantum Chests extracted from the missions
From the leaderboard, you can also view the profiles of other users, as well as the composition of their Divisions and ongoing missions.
The list shows the current **top 50** Planetary Defense users for each ranking.\
At present, the rankings are for informational purposes only and offer no rewards.
{% hint style="info" %}
Note: The information on this page reflects the current state of Planetary Defense's development. As new features are actually released and the game evolves, some details here may change, and this page will be updated to stay accurate.
{% endhint %}
---
# 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://planetary-defense-guide.gitbook.io/guide/web-game/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.
.png)