> 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/founders-items.md).
# Founders Items
Built for Visionaries
Founders Items are held by the earliest and most dedicated supporters of Clash of Coins – the people who believed in the game before it scaled.
They’re not just badges.\
A Founders Item gives advantages and long-term value that other players must earn or pay for.
***
**Total Supply: 325 Founders Items**\
\
***
#### What they provide
* Boosted activity and rewards during early phases.
* Access to exclusive perks and items unavailable to regular players.
* Long-term value sharing as the game and broader OWB Studio ecosystem grow.
#### Why they matter
Founders Items are built into the future of the game.\
New mechanics, integrations, and game modes naturally increase their utility and rarity – making them one of the strongest long-term assets in the Clash of Coins ecosystem.
---
# 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/founders-items.md?ask=&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.
