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

# Pets

Pethereum is a metaverse where there are over 100 billion unique pets. There are 25 million different physical traits which specify pet’s rarity. When the color combinations are taken into consideration, the total number of unique pets reach over 100 billion. However, Color combinations do not effect the pet’s rarity. Pets, each of which is a blockchain-based NFT, take part in various games and earn Pethereum Crystals. Each pet has 8 different physical traits with several varieties that specify the rarity of the pet.

The factors that determine the physical characteristics of pets are as follows.

| Physical Trait | Number of Varieties |
| -------------- | ------------------- |
| Hair           | 10                  |
| Eye            | 10                  |
| Ear            | 10                  |
| Mouth/Nose     | 10                  |
| Tail           | 10                  |
| Legs           | 10                  |
| Pattern        | 5                   |
| Body Type      | 5                   |


---

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

```
GET https://whitepaper.pethereum.io/gameplay/pets.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.