> For the complete documentation index, see [llms.txt](https://hyperlynx.gitbook.io/hyperlynx-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hyperlynx.gitbook.io/hyperlynx-docs/tiers-and-leaderboard.md).

# Tiers and Leaderboard

The Hunt is a watchable competition. Your cumulative points set your **rank**, and your rank sets your **tier** in the pack.

## The tiers

From the edge of the pack to the top:

| Tier        | Standing                                    |
| ----------- | ------------------------------------------- |
| **Scout**   | On the board.                               |
| **Tracker** | Rising.                                     |
| **Stalker** | Marked hunter.                              |
| **Hunter**  | Elite of the pack.                          |
| **Apex**    | The top of the pack — scarce and contested. |

Tiers are **status**. They reflect where you stand among all hunters, climb with your cumulative points, and make the hunt public and competitive.

{% hint style="info" %}
Apex is deliberately scarce. It's a position you take from someone else — that's the point.
{% endhint %}

## The leaderboard

The pack leaderboard ranks hunters by points. You can see:

* your **rank** and **percentile**,
* your **tier**, and
* where you sit relative to the pack.

What you never see is the conversion rate or the global point total — see [Overview](broken://pages/d59d34177c23c32f6846f3f54381f2ca1e393477) for why.

## Hunt cards

Your rank is shareable. Hunt cards turn your standing into an image you can post, with your referral baked in — so climbing the pack also grows it.


---

# 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://hyperlynx.gitbook.io/hyperlynx-docs/tiers-and-leaderboard.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.