> 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/use-cases/for-designers.md).

# For Designers

If you can build a game, you can launch on Kazar. Web3 is just baked in.

Launching a Web3 game today often means dealing with **wallet integrations**, **smart contract logic**, **gas fees**, **bridges**, and **marketplace setup**—none of which help you build a great game.

Kazar solves this by offering an **end-to-end publishing layer** where developers can:

* 🧩 **Deploy without writing smart contracts**\
  Just bond 50,000 KZT, and your game gets access to Kazar’s pre-built infra.
* 🚀 **Skip infrastructure complexity**\
  Wallets, transactions, token minting, and marketplaces are abstracted away.
* 🔁 **Access live-ops tooling out-of-the-box**\
  No need to build event systems or reward mechanisms from scratch.

This means developers can go from prototype to published Web3 game **without touching blockchain code**.


---

# 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/use-cases/for-designers.md?ask=<question>&goal=<user_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.