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

# Booster Packs 101

```
// Infographic here would be nice to explain the minting process
```

* **Pack Prices:**  Founder packs are **$20**, containing **5 player cards**. Each card corresponds to a random NBA player.
* **Tokens per pack:** Token counts scale linearly with price to keep the per‑dollar value constant. A $20 pack holds **1 250 tokens** in total.
* **Equal EV:** Packs are designed to fund liquidity, not to make or lose money at T0.
* **Randomised drops:** Pack odds are the same for every player. You might hit a superstar or a role player; that randomness (and the chance of a grail hit) makes opening packs exciting. All 100 players are included in the drop pool.
* **Break‑even funding:** All pack revenue goes into seeding the AMMs. There is no net profit on pack sales; instead, profits come from trading fees once the markets go live.
* **Utility & game loops:** Even commons matter: role players contribute to sets, prediction markets and future quests. Grails are valued because demand concentrates on them after launch, not because they start with more tokens.


---

# 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:

```
GET https://basketball-fun.gitbook.io/basketball.fun-docs/player-shares-and-packs/booster-packs-101.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.