> For the complete documentation index, see [llms.txt](https://arize-ar-platform.gitbook.io/arize/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://arize-ar-platform.gitbook.io/arize/welcome-to-arize.md).
# Welcome to ARize
## First 3D cross-metaverse NFT asset platform. A gateway to **Interoperable** experiences.
ARize is the leading destination to discover & purchase virtual goods for the metaverse.
We are working towards having a big database of all sorts of content, from spaceships, all the way to realistic desks, home appliances, characters etc,
**Our mission:** To truly democratize technology and content in a way that the creators are fairly compensated and the business and users have access to high-quality experiences.
**Our vision:** To provide a content layer across the Metaverse with the goal of accelerating its mass adoption.
Official Website:
Socials:
Telegram community chat:
Telegram announcements:
Twitter:
Medium:
---
# 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://arize-ar-platform.gitbook.io/arize/welcome-to-arize.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.