Getting Started
The end-to-end path through MultiSet, from your first scan to a running app with global pose and object tracking.
This page walks the full journey: scan a space, build against it with the SDK of your choice, then layer on MapSets, Map Versions, Object Tracking, and georeferencing as your project needs them. Each step links to the detailed guide.
Step 1: Create your account
Register or log in at the MultiSet Developer Portal.
Open Credentials and copy your Client ID and Client Secret. Every SDK and every REST call authenticates with this pair. See Credentials.
Calling the API from a browser? Whitelist your domain first, see Configuring Allowed Domains (CORS).
Step 2: Scan your space
A Map is a single scanned space. You can create one with a phone or bring in data from professional survey hardware, whichever suits the size and accuracy your site needs.
Option A: Scan with an iPhone or iPad
The fastest way to a working map. Install the MultiSet app on a LiDAR-equipped iPhone or iPad, walk the space, and upload. No extra hardware required.
MultiSet on the App Store : scanning, localization, content space, and geo-referencing
MultiSet on Google Play : localization, content space setup, and geo-referencing
Scanning is iOS only. Mapping requires the LiDAR sensor on an iPhone or iPad, so the Android app cannot create maps. Use it to test localization, set up a content space, and geo-reference maps you have already captured.
Maps : create and manage a map from the app
Mapping Instruction : how to walk the space while scanning
Mapping Planning : plan your coverage before you start
Mapping Equipment : what to bring for larger sites
Option B: Upload a third-party scan
Already have survey-grade data, or need to cover a large site at high accuracy? Upload an existing scan instead of rescanning.
See Third Party Scans for the full list of supported vendors, file types, and input requirements. Scanners not on the list usually work too, as long as the .e57 is structured the same way.
Step 3: Build your app
Once a map is Active, pick the integration path that matches your target platform. Every SDK handles authentication, localization, and content anchoring for you, so you rarely need to touch the REST API directly.
Android Native (Kotlin)
Native ARCore apps with no Unity dependency
Meta Wearables
Meta Ray-Ban Smart Glasses via the Meta Wearables Device Access Toolkit
All SDKs and samples are published under github.com/MultiSet-AI.
Meta Ray-Ban Smart Glasses
Wearables support ships as standalone sample apps rather than a packaged SDK. Both samples use the Meta Wearables Device Access Toolkit (DAT SDK) to pair with Meta Ray-Ban Smart Glasses, stream the live camera feed, and run VPS localization from the paired phone:
iOS sample : localization, audio turn-by-turn navigation to Points of Interest, on-lens HUD navigation on Ray-Ban Display glasses, and multiplayer pose sharing with a host running the MultiSet iOS SDK.
Android sample : localization, audio turn-by-turn navigation, and a live 2D map view.
Both need the Meta AI app with Developer Mode enabled, a pair of Meta Ray-Ban Smart Glasses, and your MultiSet Client ID and Secret. For a Unity host sharing a session with a wearable client, see Multiplayer Sample.
Going direct with the REST API
If you are working on a platform we do not ship an SDK for, or you want full control on the client side, call the API yourself. Authenticate once for a JWT, then send camera frames to the Map Query endpoint and get a 6-DoF pose back. See Localization for how single frame and multi frame queries differ and which hint parameters narrow the search.
Step 4: Grow beyond a single map
Two features handle almost every map operation you will run into as a project grows.
MapSet: cover a larger area
A MapSet joins multiple maps into one coordinate frame, so a venue too large for a single scan still behaves as one seamless space. Each map keeps its own detail while the MapSet holds the precise relative transforms between them. Query the mapSetCode and the VPS resolves the pose across every map in the set.
Add a map to a MapSet and it aligns against the whole set automatically, existing maps are untouched.
Merging Maps with Overlap : joining two scans that share physical space
Merging Maps without Overlap : joining scans that do not touch
Map Version: update a space that changed
A Map Version groups two or more scans of the same space captured at different times. One scan is the base, and every newer scan is aligned to it by the VPS. Whether you rescan a corner of a room or the entire floor, the update is added as a version instead of replacing the map.
The reason this matters: your content layer never moves. Anchors, navigation paths, and AR overlays stay authored against the base map's frame, even when the new scan comes from different hardware with a different coordinate system. MultiSet computes the transform once and translates every query transparently.
Use a MapSet to make a space bigger. Use a Map Version to make a space newer.
Step 5: Add Object Tracking
Maps are inside-out: they track where the user is inside a space. Object Tracking is outside-in: it tracks a specific physical object while the user moves around it. Reach for it when your use case needs to anchor content to a machine, product, exhibit, or prop rather than to the room.
Upload a textured GLB of the target object, and MultiSet builds a tracking map from its geometry and texture. Object Tracking runs with or without a VPS map, in the same session or a separate one, so you can localize in a building and track a machine inside it, or track the object on its own with no map at all.
Object Tracking : concepts and model requirements
How to Setup Object Tracking : end-to-end setup
Object Tracking Query : the REST endpoint
Step 6: Georeference for global pose
By default a localization result is in the map's local coordinate frame. If your app needs global pose, latitude and longitude rather than local XYZ, georeference the map. Once it is georeferenced you can pass a geoHint from device GPS to speed up localization, and convert results back to WGS84 coordinates.
There are three ways to get there:
Automatic: Walk the site with the MultiSet App, localize at several well-spread points, and let the server solve the transform from the paired VPS poses and GPS fixes. Best for outdoor maps with clear sky view. See Auto Geo-reference a Map.
Manual: Align the scan against satellite imagery by hand and set the origin and heading yourself. Use this indoors or wherever GPS is unreliable. See How to Manually Align Scans.
Inherited from the scan: If the
.e57you uploaded is already georeferenced, the map arrives georeferenced with no extra step.Georeferencing Maps : setup and GeoHint
GeoHint in Localization : using GPS as a localization prior
GeoPose Support : getting results back in global coordinates
Where to go next
Localization : query types and the hint parameters that make localization faster and more accurate
Simulation : test a map in the portal without returning to the site
Simulation Data Capture : record test data once, replay it anywhere
FAQ : common questions about the platform
Support : get help from the MultiSet team
Last updated
Was this helpful?