> 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/web-sdk.md).

# Web SDK

- [WebXR SDK](https://docs.multiset.ai/web-sdk/webxr-sdk.md): Build AR web experiences with precise indoor localization using the Multiset VPS WebXR SDK
- [Authentication](https://docs.multiset.ai/web-sdk/webxr-sdk/authentication.md): Get credentials and authorize the Multiset client before starting a session
- [Engine Integrations](https://docs.multiset.ai/web-sdk/webxr-sdk/engine-integrations.md): Adapters that connect the WebXR SDK to a rendering engine
- [Three.js Integration](https://docs.multiset.ai/web-sdk/webxr-sdk/engine-integrations/threejs-integration.md): Full end-to-end VPS integration with Three.js using ThreeAdapter
- [Needle Engine Integration](https://docs.multiset.ai/web-sdk/webxr-sdk/engine-integrations/needle-engine.md): Integrate Multiset VPS into Needle Engine projects using Inspector components or the NeedleAdapter API
- [Features](https://docs.multiset.ai/web-sdk/webxr-sdk/features.md): Capabilities and configuration beyond basic localization
- [Navigation](https://docs.multiset.ai/web-sdk/webxr-sdk/features/navigation.md): AR indoor wayfinding on top of VPS localization, with pathfinding and an arrowed floor path
- [Object Tracking](https://docs.multiset.ai/web-sdk/webxr-sdk/features/object-tracking.md): Detect and pose registered 3D objects using camera frames
- [Localization Options](https://docs.multiset.ai/web-sdk/webxr-sdk/features/localization-options.md): Tune localization accuracy with confidence filtering, hints, and background localization
- [Core Usage](https://docs.multiset.ai/web-sdk/webxr-sdk/features/core-usage.md): Use XRSessionManager with any WebGL2 renderer without Three.js
- [API Reference](https://docs.multiset.ai/web-sdk/webxr-sdk/api-reference.md): Full parameter and callback reference for all WebXR SDK classes
- [MultisetClient](https://docs.multiset.ai/web-sdk/webxr-sdk/api-reference/multisetclient.md): HTTP client for authentication, localization, and object tracking requests
- [XRSessionManager](https://docs.multiset.ai/web-sdk/webxr-sdk/api-reference/xrsessionmanager.md): Owns the WebXR session lifecycle, frame loop, camera capture, and localization timing
- [ThreeAdapter](https://docs.multiset.ai/web-sdk/webxr-sdk/api-reference/threeadapter.md): Wires XRSessionManager to a Three.js renderer
- [NeedleAdapter](https://docs.multiset.ai/web-sdk/webxr-sdk/api-reference/needleadapter.md): Needle Engine Behaviour that wires XRSessionManager to Needle's renderer
- [MapSpace](https://docs.multiset.ai/web-sdk/webxr-sdk/api-reference/mapspace.md): The VPS map coordinate frame, positioned once per localization so every child follows
- [MapAnchor](https://docs.multiset.ai/web-sdk/webxr-sdk/api-reference/mapanchor.md): Needle Engine component that positions a GameObject at a map-local coordinate after localization


---

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