> For the complete documentation index, see [llms.txt](https://docs.bullpen.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bullpen.fi/features/social-leaderboard-and-competitions/global-leaderboard.md).
# Global Leaderboard
The scoreboard for the platform.
The [Global Leaderboard](https://app.bullpen.fi/leaderboard) tracks the best traders across Bullpen in three categories. Whether you’re farming points, locking in profits, or pushing serious volume — this is where you see how you stack up against the world
#### 1. [PnL Leaderboard](https://app.bullpen.fi/leaderboard)
Who’s the most profitable trader on Bullpen?
* Tracks your realized **Profit & Loss (PnL)** across Bullpen.
* Positive PnL = climbing the board.
#### 2. [Hyperliquid Volume Leaderboard](https://app.bullpen.fi/leaderboard)
Who’s trading the largest size.
* Measures total **spot and perp trading volume**.
* Both Hyperliquid spot trades and Hyperliquid perps count.
* Perfect for whales and grinders looking to show dominance.
* Special prizes for the people on this leaderboard....
#### 3. Number of trades
* Who's really cranking on platform. Are those manual trades, or a big TWAP
#### 4. Longest Streak
* Who’s stacking the **$BULL Points** every day
---
# 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.bullpen.fi/features/social-leaderboard-and-competitions/global-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.
