> For the complete documentation index, see [llms.txt](https://kittyinu.gitbook.io/kittyinu-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kittyinu.gitbook.io/kittyinu-docs/ecosystem/nft-collection.md).

# NFT Collection

> BEP-721 · 10,000 Supply · Play-to-Earn Utility

The Kitty Inu NFT Collection consists of **10,000 unique generative characters** — each a playable asset in KittyKart and a collectible with proven on-chain rarity. NFTs are minted on BNB Chain and listed on BNB's leading NFT marketplaces.

###  Rarity Tiers

| Tier      | Supply | In-Game Boost                    | Mint Price |
| --------- | ------ | -------------------------------- | ---------- |
| Common    | 6,000  | +5% earn rate                    | 0.05 BNB   |
| Uncommon  | 2,500  | +15% earn rate                   | 0.12 BNB   |
| Rare      | 1,000  | +30% earn rate                   | 0.3 BNB    |
| Epic      | 400    | +60% earn rate + exclusive maps  | 0.8 BNB    |
| Legendary | 100    | +100% earn rate + DAO vote boost | 2 BNB      |

***

###   Utility

* **KittyKart Racing:** Every NFT is a playable character with unique stats and cosmetic traits.
* **Earn Multiplier:** Higher rarity NFTs earn more $KITTY per race win.
* **Staking Boost:** Holding an NFT boosts your staking APY by up to 25%.
* **Governance Weight:** Legendary NFT holders get 2x voting power in DAO proposals.
* **Exclusive Access:** NFT holders get early access to new game modes, merch drops, and partner events.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://kittyinu.gitbook.io/kittyinu-docs/ecosystem/nft-collection.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.