> 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/the-gamer-within-never-dies.md).
# The Gamer Within Never Dies
From late-night LAN parties to 9-to-5 routines, many of us have gone from active gamers to working professionals. But the inner gamer—the curious, creative explorer—never fades.
That’s why **Web3 gaming** resonates with a more mature audience. Despite wallets, jargon, and steep learning curves, players still choose it—not just for fun, but for **ownership, community, and purpose**.
At **Kazar**, we’ve spent half our lives in the gaming. We've seen games evolve, innovate and we won’t let this next era of web3 games be slowed by bad UX, fragmented systems, or closed ecosystems.
So we’re building **Kazar**: a connected universe of games with a shared economy, seamless progression, and real value. It’s more than tech, it’s a playground where creators thrive, players belong, and imagination leads.
***Made by the Gamers & Developers of today, for the Creators and Players of tomorrow.***
---
# 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/the-gamer-within-never-dies.md?ask=&goal=
```
`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.