> For the complete documentation index, see [llms.txt](https://zed.gambitpro.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zed.gambitpro.com/competition/13-seasons-rounds-leaderboards.md).

# Seasons, Rounds, and Leaderboards

## Season Structure

* Length: Approximately 1 calendar month per season.
* Weeks 1–3: Pack sales open.
* End of week 3: Pack sales close for the current season.
* Week 4: Pre-orders open for the next season.
* End of season: Final leaderboards lock; rewards pay out.

## Leaderboards

There are two leaderboards running simultaneously:

| Leaderboard    | Resets                      | Funded By           | Rewards                                                     |
| -------------- | --------------------------- | ------------------- | ----------------------------------------------------------- |
| Weekly         | Every 7 days (4 per season) | 45% of pack revenue | Credit prizes to top finishers                              |
| Monthly Season | End of season               | 45% of pack revenue | Credit prizes + free packs for next season + public ranking |

## How You Climb

Specifics are tuned per season, but generally rankings reflect:

* Horse performance — wins, places, and earnings by horses you own.
* Betting performance — net P\&L on the bets you place.

Your standing updates live. Check the Round Overview for the current round's top performers.

## Prize Pool Funding

Every pack purchase splits as follows:

| Share | Where It Goes              |
| ----- | -------------------------- |
| 10%   | House revenue (casino fee) |
| 45%   | Weekly prize pool          |
| 45%   | Season prize pool          |

The more packs sold in a season, the bigger the prize pools.


---

# 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://zed.gambitpro.com/competition/13-seasons-rounds-leaderboards.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.