> For the complete documentation index, see [llms.txt](https://docs.speedstar.io/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.speedstar.io/en/gameplay/lands/racecourse/bet-license.md).

# Bet License

The difference between a regular racecourse and a fully licensed racecourse is the reward amount received from betting. 

Regular racecourses will only receive compensation from the competitor's entry fee. 

However, those stadiums that have a betting license, can also earn a share of the commission from their bets, on top of the entry fees. That's why you need a license.

## Commission payout on bets.

90% of the fees from betting will return to the winner, and the system will collect all fees. 

Then the rewards will be divided into 4 parts.

1. The fees will return to the owner of the racecourse at 0.5% 
2. The fees will deliver 0.2% to the system.
3. The fees will be paid to the race winner at a rate of 0.1%.
4. **The World Grand Prix Pool** will be charged a 0.1% fee.


---

# 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://docs.speedstar.io/en/gameplay/lands/racecourse/bet-license.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.