> For the complete documentation index, see [llms.txt](https://docs.realmtoken.vip/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmtoken.vip/3.-land-protocol/zoning-and-tiers.md).

# Zoning & Tiers

To maintain a functioning economy and visual consistency, REALM.AI utilizes a strict Zoning System. A parcel's Zone dictates what can be built and how it can be monetized.

#### Zone A: Residential

* Purpose: Personal housing, private hangouts, and digital furniture display.
* Monetization: Disabled. You cannot sell items or charge entry fees here.
* Vibe: Quiet, high privacy, customizable interiors. Perfect for inviting friends to watch a stream or hang out in your "Sky Apartment."

#### Zone B: Commercial

* Purpose: Retail, Galleries, Showrooms.
* Monetization: Enabled.
* Phygital Storefronts: Sell real-world items via NFT redemption.
* Vending Machines: Sell digital wearables/skins.
* Vibe: High foot traffic, flashy signage, neon lighting allowed. This is where the economy happens.

#### Zone C: Industrial / Special

* Purpose: Headquarters, Event Stadiums, Guild Fortresses.
* Monetization: Unrestricted. Ticketed entry allowed.
* Size: These are "Estates" formed by merging multiple adjacent parcels.
* Capacity: Optimized for high-concurrency instances.


---

# 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:

```
GET https://docs.realmtoken.vip/3.-land-protocol/zoning-and-tiers.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
