> 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/quick-access/docs-for-llms.md).

# Docs for LLMs

Feed the MultiSet documentation to ChatGPT, Claude, Cursor, or any other AI tool, without pasting pages in by hand.

Building with MultiSet alongside an AI assistant? The whole documentation set is published in machine-readable form, so your assistant can read it directly.

| File                                                        | Use it when                                                                                                                                                                                                                           |
| ----------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [**llms-full.txt**](https://docs.multiset.ai/llms-full.txt) | **You are pasting context in by hand.** Every page (portal, REST API, Unity, WebXR, Quest, native iOS/Android) concatenated into one file, roughly 450 KB. Drop it into the chat or attach it as a file.                              |
| [**llms.txt**](https://docs.multiset.ai/llms.txt)           | **Your tool fetches pages itself.** An index of every page with a one-line summary and a link, so the agent reads the index first and pulls only the pages it needs. Point Cursor, Claude Code, or any MCP-style fetcher at this URL. |

### Any page as Markdown

Append `.md` to any documentation URL to get the raw Markdown instead of the rendered page:

```
https://docs.multiset.ai/fundamentals/localization/hint-floor-height.md
```

### Ask a page a question

Add an `ask` query parameter to a page URL and the response is a direct answer, with excerpts and links to the pages it came from. Useful when an agent needs one specific fact rather than a whole page:

```
GET https://docs.multiset.ai/fundamentals/localization/hint-floor-height.md?ask=what+units+is+hintFloorHeight
```

Keep the question specific and self-contained, since each request is answered on its own.

{% hint style="info" %}
These files are regenerated automatically whenever the documentation is published, so they always match the live docs. There is nothing to download or keep in sync.
{% 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/quick-access/docs-for-llms.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.