> 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/help-and-reference/16-tips-for-new-players.md).

# Tips for New Players

1. Start small. Place 1–10 credit bets while you're learning the rhythm.
2. Use the Surface Record. It's the fastest way to learn which of your horses are special.
3. Watch four or five races before betting big. You'll see how the surface and condition affect outcomes.
4. Don't chase 5-star horses blindly. A 3-star Tapeta specialist can be more profitable than a 5-star generalist on the wrong surface.
5. Set the odds format you're used to (see [Reading a Race Card §4.3](/betting-basics/04-reading-a-race-card.md)) so the numbers feel intuitive.
6. Pre-bet on upcoming races. The visibility window goes 12–48 hours ahead — you don't need to be online when your bet settles.
7. Cancel before betting closes if you change your mind. Free, instant refund.
8. Track your P\&L. Bet History (see [Bet History and P\&L](/account-and-wallet/14-bet-history-and-pnl.md)) tells you whether you're up or down across your lifetime.
9. Sales close at the end of week 3. If you want packs this season, don't leave it to the last minute.
10. Replays are free. Watch how your horses break from the gate — it's the best free scouting you'll do.


---

# 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/help-and-reference/16-tips-for-new-players.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.