> For the complete documentation index, see [llms.txt](https://archai.gitbook.io/archai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://archai.gitbook.io/archai/staking/tiers.md).
# Tiers
Tiers represent different levels that are defined based on the amount of $ARCHAI you stake. As the amount staked increases, you unlock higher tiers, which grant access to better benefits and more opportunities to participate in premium agent launches held on the platform.
### Waves
All registered participants are grouped into “waves,” with each wave consisting of a set number of participants. Waves ensure fair access to Launches by randomly assigning users to specific participation slots.
Tier 1 $ARCHAI stakers are automatically placed in Wave 1, as they receive a guaranteed allocation. Meanwhile, users in tiers 2–5 are randomly assigned to a wave, though they also have a chance to be placed in Wave 1.
Wave assignments are determined through a fair system called the **random draw mechanism**. This mechanism distributes users based on the number of **Tickets** they hold, which are tied to their tier. The more Tickets a user has, the higher their chances of being placed in Wave 1 or closer to it—ultimately increasing their likelihood of participating in a Launch.
### Allocation Weight
Allocation Weight determines the maximum amount of tokens a user can purchase during a Launch. Essentially, it defines the user's allocation. For example, if a Launch offers 1,000,000 tokens with a minimum allocation of 1,000 tokens, a Tier 5 participant with an Allocation Weight of 1 can purchase 1,000 tokens, while a Tier 3 participant with an Allocation Weight of 1.7 can purchase 1,700 tokens.
### Cool-off
The cool-off period refers to the required waiting time before a user can participate in the next Launch. For instance, a Tier 3 cool-off period of 2 means that a Tier 3 user must wait for at least two Launches to occur before becoming eligible to join the next one.
---
# 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://archai.gitbook.io/archai/staking/tiers.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.