> 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.md).

# Breeding

Breeding allows owners of Breeders to mint new Racers. Racers are bred at random according to a rarity percentage and delivered sealed for an owner to add to their kennel or sell on the secondary market.

### Breeding Facts

* Any Breeder can breed a hound of any rarity. For example, a common Breeder can breed an extremely rare Racer.
* Racers are bred at random. There is no way to predict the rarity bred of the next Racer until it is minted and opened.
* You only need to own one Breeder to breed a Racer.
* The identity and rarity of a Racer are unknown until the owner of that Racer opens the pack. You can open up your newly minted Racer in your kennel or sell it sealed for the next owner to open.
* Breeding has a fee which may change over time. It's one of the ways we protect the value of Racers on the secondary market.


---

# 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.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.
