> 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/overview/readme.md).

# Welcome to ZED Racing

**Status:** Season One (public beta) **Last updated:** 2026-05-12 **Audience:** Players. New to ZED Racing, or returning and want a refresher.

## Welcome to ZED Racing

ZED Racing is a casino-speed horse racing platform. A new race starts every 80 seconds, around the clock. You can:

* Bet on any race, whether you own a horse in it or not.
* Own horses by buying syndicate packs, building a stable, and watching them race.
* Climb leaderboards for weekly and monthly rewards.

Two things make ZED different from traditional racing:

1. It never sleeps. Races run continuously. There is always one running and one queued.
2. Horses are persistent. Every horse in the pool is a real, named entity with a career record. Over time you learn their strengths.

**Season One note.** ZED Racing is in public beta. The horse pool is capped at 1,080 horses and only single bets are available. More features (exotic bets, multi-leg parlays, expanded pool) are planned for later seasons.


---

# 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/overview/readme.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.