> 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/betting-basics/03-the-racing-schedule.md).

# The Racing Schedule

## The Three Time Tiers

| Tier   | Duration           | What It Contains                                    |
| ------ | ------------------ | --------------------------------------------------- |
| Race   | 80 seconds         | 8 horses, head-to-head                              |
| Round  | 3 hours            | 135 races — every horse in the pool races once      |
| Season | \~1 calendar month | Continuous rounds + weekly and monthly leaderboards |

Every horse in the active pool of 1,080 races exactly once per round.

## The 80-Second Race Cycle

Here is what happens in a single race window:

| Time    | What Happens                                   |
| ------- | ---------------------------------------------- |
| 0 s     | Race announced, odds posted, betting opens     |
| 50 s    | Betting closes, race begins                    |
| 50–75 s | Race plays out in four suspenseful quarters    |
| 75 s    | Results posted, winners paid, replay available |
| 80 s    | Next race begins                               |

**Important.** You have 50 seconds to place a bet from the moment a race appears. Once betting closes, no new bets are accepted on that race. You can cancel an unplaced bet up to that point — see [Placing a Bet §5.6](/betting-basics/05-placing-a-bet.md).

## Betting Lead Time

While one race is running, the next race is already open for betting. You can also look further ahead — typically you can see and bet on races 12–48 hours in advance. The visibility window is shown at the top of the lobby.

This means you don't need to be glued to the screen. Place a few bets, walk away, and check back later for the results.


---

# 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/betting-basics/03-the-racing-schedule.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.