# Kazar Revenue Model

- [Infrastructure and Staking Service](https://kazarhq.gitbook.io/kazarhq-docs/kazar-revenue-model/infrastructure-and-staking-service.md): Kazar is designed as a player-aligned, ecosystem-driven platform. We generate revenue by enabling developers to launch, monetize, and scale their games, without forcing extractive fees or comple
- [Game Passes & Feature Unlocks](https://kazarhq.gitbook.io/kazarhq-docs/kazar-revenue-model/infrastructure-and-staking-service/game-passes-and-feature-unlocks.md): Games can monetize directly by offering feature unlocks and premium passes. Designed to reward active users, sustain game operations, and align developer incentives.
- [Native Token Staking for Access](https://kazarhq.gitbook.io/kazarhq-docs/kazar-revenue-model/infrastructure-and-staking-service/native-token-staking-for-access.md): Developers and players stake $KZT tokens to unlock or maintain access to higher-tier gameplay, tools, or privileges within the Kazar ecosystem.
- [SDK/API Licensing for Studios](https://kazarhq.gitbook.io/kazarhq-docs/kazar-revenue-model/infrastructure-and-staking-service/sdk-api-licensing-for-studios.md): Provides essential development infrastructure through modular SDKs and APIs that help game developers to unlock monetization, progression, & web3 features without having to build custom web3 setups.
- [Kazar ID + Wallet Infrastructure](https://kazarhq.gitbook.io/kazarhq-docs/kazar-revenue-model/infrastructure-and-staking-service/kazar-id-+-wallet-infrastructure.md): Per-user or per-activation fees for wallet abstraction & identity infra.
- [Bonding-Based Protocol Revenue](https://kazarhq.gitbook.io/kazarhq-docs/kazar-revenue-model/bonding-based-protocol-revenue.md)
- [Game Bonding](https://kazarhq.gitbook.io/kazarhq-docs/kazar-revenue-model/bonding-based-protocol-revenue/game-bonding.md): Game Bonding is the foundational revenue mechanism that powers the Kazar protocol’s sustainability and ensures only serious developers enter the ecosystem.
- [Token Utility Engine](https://kazarhq.gitbook.io/kazarhq-docs/kazar-revenue-model/bonding-based-protocol-revenue/token-utility-engine.md): Kazar’s Token Utility Engine turns every in-game action into a revenue event—while keeping UX frictionless for players.
- [LiveOps Dashboard Subscription](https://kazarhq.gitbook.io/kazarhq-docs/kazar-revenue-model/liveops-dashboard-subscription.md): Kazar provides developers with a powerful, no-code LiveOps Dashboard—turning game management into a recurring revenue stream.
- [Deflationary Mechanics](https://kazarhq.gitbook.io/kazarhq-docs/kazar-revenue-model/deflationary-mechanics.md): Players and developers stake $KZT directly within the game or via the Kazar App to unlock higher-tier features, access deeper game layers, or get early entry into new releases.
- [Player-Side Microburns](https://kazarhq.gitbook.io/kazarhq-docs/kazar-revenue-model/deflationary-mechanics/player-side-microburns.md): Every claim, upgrade, or interaction burns small $KZT—high in volume.
- [Staking & Governance Lockup](https://kazarhq.gitbook.io/kazarhq-docs/kazar-revenue-model/deflationary-mechanics/staking-and-governance-lockup.md): Long-term lockups (3–12mo) with APR. Supports price floor + vote access.
- [Developer Incentive Tiers](https://kazarhq.gitbook.io/kazarhq-docs/kazar-revenue-model/developer-incentive-tiers.md): Developers pay KZT to feature in IGO spotlight. Tier-based, burnable.
- [Chain-Level Infra Revenue](https://kazarhq.gitbook.io/kazarhq-docs/kazar-revenue-model/chain-level-infra-revenue.md): To deliver instant, gasless gameplay across all Kazar games, we maintain a shared transaction pool funded through developer-side mechanics, removing friction for players


---

# Agent Instructions: 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:

```
GET https://kazarhq.gitbook.io/kazarhq-docs/kazar-revenue-model.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.