> For the complete documentation index, see [llms.txt](https://shiro.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://shiro.gitbook.io/docs/introduction-to-shiro.md).

# Introduction to Shiro

Shiro, the culmination of creativity and blockchain technology, presents a unique play-to-earn experience where players engage in an adventure reminiscent of nostalgic platform games but with a modern twist. Inspired by the tranquil essence of Shironeko, the "Zen Cat," Shiro is more than just a game; it's a community-driven platform that rewards its players not just with enjoyment, but with actual cryptocurrency. In the universe of Shiro, players embody various cat characters, each brimming with charm and unique abilities. As they navigate through meticulously crafted levels, they encounter challenges and collect valuable in-game items that can be converted into $SHIRO tokens. These tokens hold real-world value and provide players with a tangible reward for their gaming prowess.


---

# 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://shiro.gitbook.io/docs/introduction-to-shiro.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.
