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

# Key Motorverse elements

The Motorverse is built around a key set of elements, products and processes:

1. **The REVV Token:** $REVV is the governance and utility token at the centre of the Motorverse, finding an ever expanding set of utility as the Motorverse grows.
2. **Motorverse games and experiences:** Together with our wide set of partners, we are building the best games and experiences around digital vehicle culture. The Motorverse is designed to be a collaborative effort between many ecosystem partners. To simplify the partnership process, the team has developed a simple process on how to partner with new and existing ecosystem players.
3. **Motorverse licensing and metadata standards:** In order to ensure a seamless experience, asset interoperability plays a pivotal role in the ecosystem. To that end, the Motorverse team is working with vehicle manufacturers to develop a key set of interoperability standards related to licensing and vehicle metadata that will be used across the Motorverse. This is a fundamental step to make interoperability between projects and products possible. 
4. **The Motorverse Hub:** To support the transition to a more integrated ecosystem, the REVV Motorsport website is replaced by the Motorverse Hub, the connecting layer between all Motorverse experiences. On the Hub, users will be able to purchase digital cars, explore games and experiences compatible with their vehicles, and browse content related to the wider ecosystem. 


---

# 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://motorverse.gitbook.io/revv-litepaper/the-motorverse/key-motorverse-elements.md?ask=<question>&goal=<endgoal>
```

`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.