> For the complete documentation index, see [llms.txt](https://kazarhq.gitbook.io/kazarhq-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kazarhq.gitbook.io/kazarhq-docs/kazar-revenue-model/bonding-based-protocol-revenue/token-utility-engine.md). # Token Utility Engine Kazar’s Token Utility Engine turns every in-game action into a revenue event—while keeping UX frictionless for players. #### ⚙️ Native Token Minting Each bonded game gets the ability to mint its **own native token** (optional), mapped and powered by KZT. These tokens can be used for: * Rewards * Upgrades * Seasonal currencies > 🔸 Minting costs a **micro-fee in KZT**, ensuring network demand scales with usage. #### 🛠️ Monetization Hooks Out-of-the-box support for: * Battle Passes * Cosmetic Upgrades * NFT Drops * XP Boosts All mints/claims are **gasless for players**, powered by the dev’s bonded pool. #### 🔄 Invisible but Powerful * Every transaction triggers **micro-KZT burns**, invisible to players but massive in aggregate. * Devs don’t need to write contracts — the engine is plug-and-play with Unity/WebGL SDKs. * Token supply + economics managed through Kazar’s dashboard, no blockchain experience needed. --- # 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://kazarhq.gitbook.io/kazarhq-docs/kazar-revenue-model/bonding-based-protocol-revenue/token-utility-engine.md?ask=&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.