> 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/infrastructure-and-staking-service/sdk-api-licensing-for-studios.md).

# SDK/API Licensing for Studios

**Core Features Enabled**

* Wallet login, session management, and user identity
* In-game token rewards and marketplace interactions
* Quest systems, progression logic, and reward gates
* Game registration, analytics tracking, and KYC workflows (for real-money setups)

#### Monetization Model

* **Usage-based fees**: Developers are charged a small % fee (e.g., 1–3%) on monetized transactions triggered via the SDK (pass claims, drops, upgrades, etc.)
* **Freemium access**: Early-stage and indie developers can integrate basic SDK features for free. As usage scales, premium modules unlock via staking or fee-sharing.

#### Benefits

* Removes need for custom smart contracts or backend infra
* Greatly reduces time-to-market for new games
* Ensures Kazar retains value flow from each integrated title

By making blockchain-native infrastructure as plug-and-play as possible, Kazar helps developers focus on building great games while still benefiting from monetization, ownership, and ecosystem growth.


---

# 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/infrastructure-and-staking-service/sdk-api-licensing-for-studios.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.