> 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/04-reading-a-race-card.md).

# Reading a Race Card

Every race has a Race Card that shows you everything you need to decide a bet.

## Header

The header shows:

* Race number (its position in the current round).
* Theme — one of five cosmetic settings: CyberAbyss, NeoSahara, Skyfall, TVC, Vulcan, in either Day or Night variant. Themes are visual flavour only.
* Surface — the track surface for this race. This affects outcomes (see [Track Surfaces and Conditions](/owning-horses/11-track-surfaces-and-conditions.md)).
* Condition — Fast / Standard / Yielding / Heavy. This also affects outcomes (see [Track Surfaces and Conditions](/owning-horses/11-track-surfaces-and-conditions.md)).
* Distance — 1,000 metres for every Season One race.
* Countdown — time until betting closes.

## Runners List

Each of the 8 runners is shown with:

| Column         | Meaning                                                                                                                  |
| -------------- | ------------------------------------------------------------------------------------------------------------------------ |
| Gate           | The starting gate number (1–8).                                                                                          |
| Horse          | Name, colour silk, and bloodline.                                                                                        |
| Star Rating    | 1–5 stars indicating overall quality.                                                                                    |
| Form           | Recent finish positions, most recent on the right.                                                                       |
| Surface Record | Win/Place stats on this surface (see [Understanding Your Horses §10.2](/owning-horses/10-understanding-your-horses.md)). |
| Jockey         | Who's riding.                                                                                                            |
| Odds           | Win odds, in your chosen format (see §4.3 below).                                                                        |

## Odds Format

Odds are shown in either Decimal (European) or American format. Change this any time in Profile → Preferences.

| Format   | Example | What it Means                                           |
| -------- | ------- | ------------------------------------------------------- |
| Decimal  | 4.50    | A 1-credit bet returns 4.50 credits total (3.50 profit) |
| American | +350    | A 100-credit bet returns 350 credits profit             |

## Currency Display

All amounts — stakes, odds payouts, balances, prize pools — are shown in USD-equivalent credits, regardless of which crypto your partner casino settles in. This keeps the numbers readable.

**Note.** Underlying settlement still happens in whatever token your casino account uses. ZED handles the conversion behind the scenes.


---

# 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/04-reading-a-race-card.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.