# Use Cases

- [For Designers](https://kazarhq.gitbook.io/kazarhq-docs/use-cases/for-designers.md): If you can build a game, you can launch on Kazar. Web3 is just baked in.
- [For Developers](https://kazarhq.gitbook.io/kazarhq-docs/use-cases/for-developers.md): Kazar turns every game into a business model—with zero Web3 friction.
- [AI-Assisted Game Management](https://kazarhq.gitbook.io/kazarhq-docs/use-cases/ai-assisted-game-management.md): In Kazar, AI isn’t about generating fluff—it’s about helping you build better games.
- [Unified Player Onboarding](https://kazarhq.gitbook.io/kazarhq-docs/use-cases/unified-player-onboarding.md): Gamers don’t need to understand Web3 to enjoy it. With Kazar, they don’t even notice it.
- [Scalable Game Launch Infrastructure](https://kazarhq.gitbook.io/kazarhq-docs/use-cases/scalable-game-launch-infrastructure.md): The future of Web3 gaming isn’t about reinventing infrastructure, it’s about making infrastructure disappear.


---

# 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/use-cases.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.