> For the complete documentation index, see [llms.txt](https://zelix-io.gitbook.io/zelix/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zelix-io.gitbook.io/zelix/zelix-technology/vr-experience-space.md).
# VR Experience Space
## ZELIX Metaverse has default space with in VR experience
ZELIX's metaverse does not start from empty land. The foundation initially prepares basic sights and entertainment for users. By providing various spaces such as amusement parks, concert halls, and shopping centers in advance, users can predict what they can do with empty spaces, helping to fill new spaces.
Among the VR experience spaces, the amusement park provides independent VR images for each ride, and users use a small amount of ZELIX tokens to use them. And by installing billboards in every corner of the amusement park, companies can use ZELIX to place advertisements, thereby connecting users and companies.
---
# 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://zelix-io.gitbook.io/zelix/zelix-technology/vr-experience-space.md?ask=&goal=
```
`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.