> For the complete documentation index, see [llms.txt](https://omniaverse.gitbook.io/omniaverse/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://omniaverse.gitbook.io/omniaverse/about/introduction.md).

# Introduction

OmniaVerse is a dynamic and innovative Web3 gaming, arts, collectibles, and entertainment ecosystem at the forefront of revolutionizing the digital landscape. With a visionary approach, a completely live ecosystem, and demonstrated record of delivery, OmniaVerse is bridging the gap between traditional forms of entertainment and the decentralized Web3 world, offering seamless integration of cutting-edge blockchain technology with familiar gaming and entertainment experiences.

The OmniaVerse ecosystem solves the current fragmentation of current Web3 gaming efforts by integrating all elements into a single cohesive platform.  OmniaVerse consists of a full technology stack including our true zero-gas blockchain, simple onboarding process, game distribution/asset management platform, and tons of high quality content from ourselves and our many partners.

<figure><img src="https://1571189094-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaexJlM8QYrZJYcnJGWWE%2Fuploads%2Fdq3C5FO4TFTpqc5ZMgId%2FOmniaVerse%20Logo%20Text%20with%20Black%20Text.png?alt=media&amp;token=39a729cc-5e48-497e-a516-8168863870f1" alt="" width="375"><figcaption></figcaption></figure>


---

# 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://omniaverse.gitbook.io/omniaverse/about/introduction.md?ask=<question>&goal=<user_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.