> For the complete documentation index, see [llms.txt](https://petto.gitbook.io/petto/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://petto.gitbook.io/petto/characters/petto-rarity-types.md). # Petto Rarity Types Beans can transform into one of the following Pettos: 🔴**ULTRA Pettos - \[ウルトラ].** \ **Rarity:** extremely rare.\ Real animals that are on the red list of endangered species. The number of available Ultra Pettos is directly linked to their actual population in real life. Ultra Pettos have distinct powers that are represented visually and by their stats. 🟠**KAIKI Pettos - \[怪奇]** \ **Rarity:** rare to extremely rare.\ Fictional characters, supernatural beings that don't exist in real life. Mythical creatures originate from ancient mythologies, stories, folklore, films, etc. 🟢**KIMI Pettos** **- \[**君/きみ**]**\ **Rarity:** frequent to rare.\ Animal races that we all know from life such as Cats, Dogs, or any other animal you can think of. --- # 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://petto.gitbook.io/petto/characters/petto-rarity-types.md?ask=&goal= ``` `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.