> For the complete documentation index, see [llms.txt](https://docs.multiset.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.multiset.ai/unity-sdk/meta-quest.md).

# Meta Quest SDK

MultiSet VPS for Unity projects targeting Meta Quest headsets

The MultiSet Quest SDK is a Unity development kit built specifically for Meta Quest headsets. It connects your mixed reality application to MultiSet's Visual Positioning System for centimeter-accurate real-time localization, pose visualization, and camera access.

### What's inside

1. [**Installation Guide**](/unity-sdk/meta-quest/installation-guide.md): requirements, package import, and scene setup for Quest.
2. [**Map Mesh Downloader**](/unity-sdk/meta-quest/map-mesh-downloader.md): fetch and display a map's mesh inside the headset.
3. [**Authentication**](/unity-sdk/meta-quest/authentication.md): authenticate the SDK with your Client ID and Client Secret.
4. [**Sample Scenes**](/unity-sdk/meta-quest/sample-scenes.md): localization, single frame localization, object tracking, and navigation samples.
5. [**API Reference**](/unity-sdk/meta-quest/api-reference.md): the manager classes the Quest SDK exposes.

{% hint style="info" %}
Building for handheld iOS or Android instead? See the [AR Foundation SDK](/unity-sdk/ar-foundation.md).
{% endhint %}


---

# 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://docs.multiset.ai/unity-sdk/meta-quest.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.