> For the complete documentation index, see [llms.txt](https://guide.muzzle.run/muzzle-run-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.muzzle.run/muzzle-run-docs/muzzle-run-racing/breeding/rarity-distribution.md).

# Rarity Distribution

When you breed a Racer it will have a rarity attached to it. The rarer the hound then the faster and more successful it will be without training. Rarer hounds can also enter exclusive tournaments with added prize pools. The chances of breeding a Racer of the different rarities are based on the following distribution.

* Common: 80%
* Rare: 18%
* Very Rare: 1.14%
* Extremely Rare: 0.13%

All Breeders have the equal potential to breed a Racer of any rarity. For example a common Breeder has the same chance as a rare Breeder to breed an extremely rare Racer.


---

# 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://guide.muzzle.run/muzzle-run-docs/muzzle-run-racing/breeding/rarity-distribution.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.