> For the complete documentation index, see [llms.txt](https://docs.dexkit.com/welcome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dexkit.com/welcome/our-token/utilities.md).

# Utilities

What can you do, currently, holding our currency?

🟢Hold 1,000 KIT tokens on any network \[check [Contract addresses](https://docs.dexkit.com/welcome/our-token/contract-addresses.md)] for DexKit signature removal on DApps, DApp design mint as NFT, among other amenities.

🟢Hold 20 KIT to customize Kittygotchi NFT pet in several levels on Binance Smart Chain, Polygon and Ethereum networks;

🟢50% of [Kittygotchi](https://app.dexkit.com/kittygotchi) earnings is used to buyback and provide liquidity on KIT token on Binance Smart Chain, Polygon and Ethereum networks;

🟢Hold 500 KIT to receive fees on Aggregator;

🟢Hold 750 KIT to receive 90% discount on trading fees using the [DSWAP aggregator](https://swap.dexkit.com/);

🟢70% of aggregator fees are used to buyback and liquidity on $KIT token;

🟢Hold 1,000 KIT tokens to propose and vote on [Snapshot space](https://snapshot.org/#/dexkit.eth). Also get access to private Discord server for governance.


---

# 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://docs.dexkit.com/welcome/our-token/utilities.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.
