Noughty Reality
Noughty Reality is a platform for spatial capture. A space is scanned on a device, processed into a structured virtual tour, and served back to whatever needs to show it.
Two SDKs sit at opposite ends of that pipeline. They are separate products with separate purposes, separate authentication, and separate APIs — pick the one that matches what you are building, rather than reading both.
Products
| Product | What it does | Platform |
|---|---|---|
| Web SDK | Reads finished tours and renders them in your app | Web |
| iOS SDK | Captures spaces — panoramas, floor plans, upload | iOS |
Web SDK
@thenoughtyfox/noughty-tours-web-sdk is a read-and-render SDK. It gives you a
typed data client for the Noughty Tours API plus four ready-made React screens,
so you can list tours, manage them, and show the panorama viewer.
Authentication is by JWT: your backend signs a short-lived token with its own key and publishes the public half as a JWK Set, and we verify against that. Your signing key never leaves your servers.
Start with Quick start, or read Core concepts first for the tour → floor → room → scan model the client returns.
iOS SDK
NoughtyToursSDK is a capture SDK. It drives the device that produces a tour in
the first place — LiDAR structure capture, panorama capture, local storage and
background upload — and vends the capture screens as view controllers you push
onto your own navigation stack.
Authentication is by device attestation: the device attests against your App ID with App Attest, scoped to an organisation you supply. There is no JWT and no JWKS.
Start with the iOS SDK overview.
Which one do I need?
- Building an app that scans a property — a surveyor, agent or field technician pointing a phone at a room? That is the iOS SDK.
- Building a site or web app that shows a tour someone already captured — a listing page, a portal, a customer-facing viewer? That is the Web SDK.
- Doing both? They are wired together by the platform, not by your code. Capture with one, embed with the other; nothing is shared between the two integrations but the tour itself.