Spatial development docs for scenes, data, and app access.
Move from captured spatial material to a Five SDK scene, Team-scoped Developer app credentials, OpenAPI data, and reviewed reconstruction workflows.
spatial.dev.stack
0 guides mapped
capture.to.runtime
live pathScene source
work.json
Spatial layers
panorama, depth, point cloud
Runtime path
Five SDK render loop
Data gateway
OpenAPI response stream
Scene runtime
@realsee/five
Gateway
/open/v3
Credentials
App request
Integration paths
Choose by the work you are doing.
The primary paths keep scene runtime, Team access, API data, and reviewed reconstruction separate enough to reason about.
Render
Run a Five SDK scene
Load a work.json file, mount Five, and verify a browser scene before adding product UI.
@realsee/five
Access
Request a Developer app
Keep Team ownership, App request state, UserCode, and provisioned credentials in the same workflow.
Team scoped
Data
Call OpenAPI endpoints
Read VR, interaction, branding, and asset data through provisioned Developer app credentials.
/open/v3
AI review
Prepare Argus reconstruction
Follow the reviewed upload, token, reconstruction, and polling flow for AI-generated spatial output.
Reviewed
Full catalog
All guides by product surface.
Use the catalog when you already know the SDK, gateway, or workflow you need.