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

# Meta Brawl

![](/files/IgkNLGoHPFtZVpBt1FBw)

## Our Mission

The gaming industry is immense but flawed, being built on one-sided models that restrict user ownership and stifle player-driven economies. We believe players should truly own their items in any game; moreover we believe players should be rewarded for the time and effort they invest into playing a game and contributing to that game’s community in a positive manner. This is why we are building Meta Brawl. We know games can be more, so we are busy building a game where every battle you fight, and every item you buy is designed to contribute to a long-term, sustainable, real-value economy. The items you own are set up to have greater utility beyond just playing the game as you can trade/sell them with anyone, even outside the game. No one should be able to take away what belongs to you, a principle made achievable with the help of Binance's smart chain technology.


---

# 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://metabrawl.gitbook.io/meta-brawl/meta-brawl.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.