> For the complete documentation index, see [llms.txt](https://docs.clashofcoins.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.clashofcoins.com/game-items-and-open-economy.md).

# Game Items & Open Economy

#### **Ownership**

Key game items – Buildings, Founders, and future collections, live directly in players’ wallets.\
They’re yours to use, trade, upgrade, or hold. Full control.

#### **Market Dynamics**

Buildings are limited-supply assets that players actively trade.\
The market reflects strategy, demand, and scarcity, not artificial pricing.

#### **Strategic Value**

Upgrades improve gameplay performance and increase market value.\
Every choice – what you build, how you upgrade, what you trade directly impacts both your map position and the broader economy.

***

### Core Item Types

[**Buildings**](https://docs.clashofcoins.com/game-items-and-open-economy/buildings-items.md)**:**

Define your strategy. Attack, defend, scale income. Limited supply, tradable, upgradeable.\
More collections with different stats and roles are coming soon.

[**Founders**](https://docs.clashofcoins.com/game-items-and-open-economy/founders-items.md)**:**

Early-supporter assets with long-term perks and exclusive utility across the ecosystem.

***

#### **Why It Matters**

Value in Clash of Coins comes from one place – real player activity and the growth of the game itself.\
As the player base expands, demand for items grows with it.\
When you play, trade, or invest inside the ecosystem – you’re participating in an open economy shaped directly by the community.


---

# 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.clashofcoins.com/game-items-and-open-economy.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.
