> 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/core-offerings/kazar-game-layer-uni-layer.md).

# Kazar Game Layer (Uni-Layer)

The **Kazar Game Layer**, also known as the **Uni-Layer**, is the backbone of our ecosystem. It enables all games built on Kazar to plug into a **shared infrastructure**—unifying player identity, progression, rewards, and assets across titles.

Instead of building isolated game loops and wallets from scratch, developers can focus on gameplay and creativity while **tapping into a networked layer** that handles:

* ✅ **Cross-Game Progression**: Player XP, achievements, and perks travel across Kazar games.
* ✅ **Shared Wallet Layer**: One wallet, one inventory—usable across all titles in the ecosystem.
* ✅ **Reward Distribution System**: Players earn universal rewards that hold value across multiple games.
* ✅ **Matchmaking & Live-Ops Hooks**: Built-in APIs for multiplayer logic, game events, and engagement loops.

This modular layer **reduces development time**, improves retention, and creates a powerful **network effect**—where every new game enhances the value of all others.

> **The Uni-Layer turns isolated games into a connected world.**


---

# 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/core-offerings/kazar-game-layer-uni-layer.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.