> For the complete documentation index, see [llms.txt](https://docs.cod3x.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cod3x.org/cdx-token/battlepass.md).

# Battlepass

### Season Structure

* Duration: 90 days per season
* Levels: 50 levels to complete
* XP required: \~50,000 XP total
* Target pace: \~555 XP per day

### Two Tracks

#### Free Track

Available to everyone. Earn CDX, cosmetics, and badges just by playing.

* Total rewards: \~12,500 CDX + cosmetics

#### Premium Track

Unlocked by staking at PRO tier (5,000+ CDX). Get both tracks!

* Additional rewards: \~40,000 CDX
* Exclusive cosmetics: Animated frames, legendary skins
* Total (both tracks): \~52,500 CDX

### Milestone Rewards

Every 10 levels unlock special milestone rewards:

* Level 10: Milestone badge + bonus CDX
* Level 20: Exclusive title + bonus CDX
* Level 30: Premium cosmetics + bonus CDX
* Level 40: Elite rewards + bonus CDX

Level 50: Season Complete badge + legendary rewards


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cod3x.org/cdx-token/battlepass.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
