> For the complete documentation index, see [llms.txt](https://grizzyfi.gitbook.io/grizzyfi-launchpad/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://grizzyfi.gitbook.io/grizzyfi-launchpad/whitepaper/tier-system.md).

# Tier System

Grizzy Fi's Enhanced Tiered System is designed to offer unique advantages to investors who actively engage with our ecosystem. This system consists of three tiers: Cubby, Panda, Grizzly each featuring its own exclusive benefits. Here’s a detailed overview of each tier:

**Cubby - 100 tokens**

* 25% chance to quality for allocation
* VIP lounge access

**Panda - 250 tokens**

* 50% chance to qualify for allocation 
* Larger allocation size
* VIP lounge access

**Grizzly - 500 tokens**

* Guaranteed allocation 
* Maximum allocation size
* Whitelist for all IDOs and NFT sales
* VIP lounge access
* Voting power in governance\\
* Bonus token and airdrop eligibility 


---

# 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://grizzyfi.gitbook.io/grizzyfi-launchpad/whitepaper/tier-system.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.