> For the complete documentation index, see [llms.txt](https://whitepaper.arcadecolony.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.arcadecolony.com/token-overview.md).

# Token Overview

## **COLONY Token**

The Arcade Colony Governance Token, known as COLONY, will serve as the staking, reward, and governance token within the Arcade Colony Governance (ACG) ecosystem. All games that are listed on the Arcade Colony directory will need to accept COLONY tokens as a form of payment.&#x20;

### COLONY Utility

The COLONY token will have several primary uses within the Arcade Colony ecosystem:

* Distribution as rewards in games
* Earning staking rewards
* Maximizing game rewards
* Reducing network fees
* Upgrading various player owned aspects of the game
* Participating in platform governance
* Minting new SCRIPT tokens (designed to stay worth approximately $1) through burning of COLONY – more about SCRIPT in the following section

## **SCRIPT Token**

The SCRIPT token will be pegged to product in Arcade Colony and be acquired by burning COLONY tokens for a set amount of SCRIPT tokens based on market conditions. 1 SCRIPT token will be accepted as $1 USD of product in the Arcade Colony ecosystem.&#x20;

### **SCRIPT Utility**

The SCRIPT token will have several primary uses within the AC ecosystem:

* Buy and sell assets from in-game shops
* Buy, sell, and rent NFTs on the Arcade Colony Marketplace
* Use cases will be built into each game&#x20;


---

# 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://whitepaper.arcadecolony.com/token-overview.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.
