> 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/the-usdbig-token.md).

# The $BIG Token

$BIG is the ecosystem token of BIG Indie Games. Its role is to connect the gaming portfolio, community, treasury, and Web3 layer of the project.

$BIG is not required for regular players to enjoy our games. This is important. We want mainstream players to enter through gameplay, not through complicated crypto onboarding.

Over time, $BIG may be used for ecosystem rewards, holder benefits, special campaigns, community incentives, and selected game-related Web3 features.

The purpose of $BIG is to give the community a transparent Web3 layer connected to the long-term success of BIG Indie Games.

| Token Name       | BIG Indie Games                            |
| ---------------- | ------------------------------------------ |
| Ticker           | $BIG                                       |
| Network          | Ethereum                                   |
| Contract Address | 0x1337B164D318234ccafc3B06c726f522314B2799 |
| Token Category   | Gaming / GameFi / Game Studio              |


---

# 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/the-usdbig-token.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.