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

# About

BIG Indie Games is built on one simple belief: great games should come first.

We are not building games only for crypto users. We are building for regular gamers: players who want fun gameplay, smooth access, strong progression, competition, collectibles, rewards, and a reason to come back every day.

$BIG is the Web3 layer connected to this vision. It is designed to grow together with the BIG Indie Games ecosystem, while the main focus stays clear: build games people genuinely want to play, generate real revenue, and use part of that revenue to support the long-term strength of $BIG.

Our mission is to create a gaming brand where traditional gaming revenue and Web3 transparency work together.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bigindie.games/about.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 `automate deployments from our CI pipeline` 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.
