> For the complete documentation index, see [llms.txt](https://cells-nft.gitbook.io/cells/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cells-nft.gitbook.io/cells/map-zones/exclusive-cells-zone.md).

# ELEMENTAL ZONES

![ZONE distributions all around the world.](/files/-MhpkqPeKztpgGK2yi-v)

We created exclusive ELEMENTAL ZONES specially dedicated to our community, cell holders have a chance to get a cell located at one of this areas.\
\
Zones come in 2 sizes: 9 and 25 cells clusters. \
\
This means if one of the CELLS belongs to a specific zone it will have an unique overlay specially dedicated to that specific ELEMENT. We created a set of 4 overlays identified as WATER, EARTH, FIRE AND AIR.\
Exclusive zones will be visible from afar as you may see in the picture above.\
\
A few zones will be minted directly to The Cells wallet and will serve for several community activities and competitions.


---

# 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://cells-nft.gitbook.io/cells/map-zones/exclusive-cells-zone.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.