> For the complete documentation index, see [llms.txt](https://whitepaper.pethereum.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.pethereum.io/gameplay/rarity.md).

# Rarity

[Pets](/gameplay/pets.md) in the Pethereum metaverse have various physical characteristics, such as feather types, ears, and more. There are 25 million combination of 8 different physical traits which specify pet’s rarity, excluding main color and secondary color. When the color combinations are taken into consideration, the total number of unique pets reaches over 100 billion. However, color combinations do not effect the pet’s rarity.

The more common a pet's physical trait, the less rare it is. Pet rarity levels can also be seen in the marketplace. Rare pets can be sold for much higher prices.

Pet rarity is determined by their 8 physical traits, and each trait can have a common, uncommon, rare, epic, or legendary rarity level.

Thanks to this diversity, there are over 100 billion pets which have different physical traits and colours.


---

# 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://whitepaper.pethereum.io/gameplay/rarity.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.