> 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/buildings-items.md).
# Buildings Items
**What They Are?**
Building Items are strategic in-game assets (offensive, defensive, and special) that define how you expand, defend, and fight on the world map.\
\
**What they do**
* Increase income from your provinces
* Strengthen defenses on key territories
* Enable strong attacks to break enemy positions
**How to get them**
* Seasonal distributions (main source)
* Limited loot boxes and rewards
* Player-to-player trading
Supply is intentionally limited, so the right Building Item is not something you spam, it’s something you hunt for and build around.
In the near future, there will be **multiple Building Item collections** with different stats and characteristics, giving players more ways to fine-tune their strategy.
---
# 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/buildings-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.
.png?alt=media&token=fdc94ae8-fd5d-43a2-a480-8fa1d389539c)