> 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/unified-player-onboarding.md).

# Unified Player Onboarding

Gamers don’t need to understand Web3 to enjoy it. With Kazar, they don’t even notice it.

Most Web3 games still expect players to install wallets, understand chain switching, sign transactions, and manage tokens—**just to press play.** It’s a broken loop that keeps 90% of real gamers out.

Kazar fixes this with **frictionless onboarding built into the core**:

* 🧾 **Login with email, social, or wallet**\
  Players can jump in without needing a wallet at all—progress and rewards are synced invisibly.
* 🔄 **Unified identity across all games**\
  One profile, one wallet, one inventory—usable across every Kazar-powered title.
* ⚙️ **Abstracted transactions & gas**\
  No more scary MetaMask popups. Players transact with a simple click. Gas fees? Covered or abstracted in most flows.
* 📱 **Mobile-first UX**\
  Fully optimized for mobile WebGL and native experiences—because real gamers don’t live in Chrome wallets.

Kazar removes every hurdle between **"I found this game"** and **"I’m having fun"**.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://kazarhq.gitbook.io/kazarhq-docs/use-cases/unified-player-onboarding.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 `build a script that syncs our docs to a CMS` 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.