> 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/developer-incentive-tiers.md).

# Developer Incentive Tiers

### 🔁 Core Revenue Streams

#### 1. **Game Bonding (IGO)**

* Developers bond **50,000 KZT** to launch games.
* **10% of bonded tokens are burned**, the rest are locked for 6–12 months.
* This model ensures quality, deflation, and consistent demand for KZT.

> 💡 A portion of bonded KZT is recirculated to the ecosystem via grants and rewards.

***

#### 2. **Marketplace Fees**

* 2% fee on NFT/item transactions:
  * **1% burned (deflationary)**
  * **1% redistributed to KZT stakers**

> 💡 The marketplace is shared across all Kazar games, enabling liquidity and monetization at scale.

***

#### 3. **Monetization SDK Usage**

* Developers using the One-Click Monetization SDK may opt into:
  * **Revenue-share tiers** (based on volume)
  * **Premium API access for scaling titles**

> 💡 We keep fees low—only apply charges above certain thresholds (to support indies).

***

#### 4. **Premium AI Tools & Compute**

* Advanced AI features (e.g., simulation, smart logic tuning, live NPCs) are unlocked via:
  * **KZT staking**
  * Optional **usage-based fees** for heavy compute workloads

***

### 🎯 Designed for Alignment

Kazar does **not extract revenue at player level**. Instead, we align monetization with:

* Developer success (launches, sales, sessions)
* Token utility (burns, locks, staking)
* Long-term community ownership

> **Revenue flows back into staking, grants, and deflation. The more builders succeed, the more the ecosystem grows.**


---

# 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://kazarhq.gitbook.io/kazarhq-docs/kazar-revenue-model/developer-incentive-tiers.md?ask=<question>&goal=<endgoal>
```

`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.