> For the complete documentation index, see [llms.txt](https://docs.global-entertainment-token.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.global-entertainment-token.org/ja/4-purodakutotoekoshisutemu/46-get-citymetabsu.md).
# 4.6 GET City（メタバース都市構想）【構想中】
GET Cityは、現実とバーチャルが融合した次世代型エンターテイメントメタバース都市の構想です。土地、施設、体験をトークンで管理し、参加者が経済的にも文化的にも貢献できる空間を提供します。
**構成要素（予定）：**
* バーチャルライブ会場、映画館、展示スペース
* 土地や建物のNFT化と分離所有モデル
* GETトークンで投票／支払い／ステーキングが可能
* リアルイベントとの同時体験（双方向連携）
---
# 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.global-entertainment-token.org/ja/4-purodakutotoekoshisutemu/46-get-citymetabsu.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.
