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

# Packs

#### Tiers & Rarity

Packs allow you to obtain cards used in tournaments.\
Each card comes with a specific **rarity**, which directly impacts the **points multiplier** you receive during tournaments.

There are four rarity tiers:

* **Common**
* **Rare**
* **Epic**
* **Legendary**

Higher rarity cards provide stronger multipliers, giving you a competitive advantage in tournaments.

#### Driver Cards & Tokens

Driver cards are linked to **tokens**.\
When you open a pack and receive a driver card, you also receive a number of tokens associated with that driver.

The amount of tokens you receive depends on the card’s rarity:

* **Common:** 500–1,000 tokens
* **Rare:** 1,000–2,000 tokens
* **Epic:** 2,000–5,000 tokens
* **Legendary:** 5,000–10,000 tokens

#### Purchasing Packs

To purchase packs, you need **TRB**, the in-game currency of **f1.fan**.\
TRB can be acquired by purchasing it with **Solana** and is used exclusively within the game.


---

# 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://f10.gitbook.io/f1-docs/overview/packs.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.