> 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/motorverse-interoperability-standards.md).

# Motorverse interoperability standards

The Motorverse is bringing the concept of car ownership to the digital age. And just as in the real world, we want you to be able to drive your car across different places. To do that, the Motorverse aims to bring together the best games and experiences for you to drive your car in. Whether built in-house or via partnerships and collaborations, we will provide you with a seamless ride across experiences.&#x20;

That’s why interoperability is pivotal for our ecosystem. We define interoperability as being able to use the same digital object in two or more different games/experiences in the same or different ways. In other words, our goal is that cars, parts, tracks and other assets will become usable, and can easily and permissionlessly be moved, across game and entertainment experiences in the Motorverse

In order to ensure a smooth transition towards a more interoperable experience of your assets, the Motorverse is developing a set of metadata standards for cars, bikes, and other assets. Together with other game developers, car brands, and institutions we’re building an alliance to ensure that interoperability is tackled in a systematic and encompassing manner.

At the same time, we are working to create new legal standards for licensing contracts that allow assets to be moved across experiences without being blocked by IP rights.


---

# 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/motorverse-interoperability-standards.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.
