3D • VR • AR • AI • GAME ASSETS
Build beyond the screen.
Explore APIs for the next dimension.
Your field guide to spatial 3D APIs, virtual reality, augmented reality, spatial AI, and the assets that bring worlds to life.
Make scenes, coordinates, and model delivery understandable before adding another dimension of complexity.
Design a complete immersive journey, from deliberate session entry to clear interaction and a useful return to the page.
Connect candidate geometry to intentional placement, stable relationships, and visual integration that handles uncertainty.
Build scene-understanding features that preserve context, acknowledge uncertainty, and make bounded decisions.
Turn source artwork into repeatable, testable scene releases with clear asset budgets, validation, and recovery paths.
A model, a tracked pose, and an AI prediction are not the same thing. Learn how to connect them without losing their meaning.
An illustrative local coordinate study. Enable JavaScript for the interactive view.
A working, browser-side coordinate study. Rotate the cube to explore its axes. This is a visual learning aid, not live tracking data.
Start with what the browser can actually do
Check capabilities, build a small working loop, and keep the ordinary page useful. Our guides focus on practical decisions—not imaginary endpoints.
// Feature detection, not a session or a hosted API call.
async function checkSpatialSupport() {
if (!window.isSecureContext || !navigator.xr) {
return { vr: false, ar: false };
}
const modes = ['immersive-vr', 'immersive-ar'];
const results = await Promise.all(modes.map(async (mode) => {
try { return await navigator.xr.isSessionSupported(mode); }
catch { return false; }
}));
return { vr: results[0], ar: results[1] };
}Runs locally. Does not start an immersive session.
Follow the learning paths to WebXR, OpenXR, and glTF. Official references sit alongside implementation questions and project-level tradeoffs.
Separate rendering, device access, geometry, and semantic predictions. Give unsupported features an understandable fallback.
Work through placement, interrupted sessions, content validation, accessibility, and the handoffs that make a scene maintainable.
Ideas for the next dimension
Build clearer 3D data contracts with named coordinate spaces, durable object identities, and a testable scene-loading workflow.
Read the field note
Plan browser support, deliberate session entry, clear interactions, recovery, and a useful non-immersive experience.
Read the field note
Design scene-understanding features that preserve context, confidence, and the distinction between inference and fact.
Read the field noteNew to spatial development? Start with scene identity and coordinate conventions, then choose an immersive route. Building AR placement? Read hit testing before anchors and visual occlusion. Preparing game content? Follow the model-delivery guide into validation, quality variants, and repeatable releases. Each path is designed to turn a broad topic into decisions you can test.
Clear answers. Better starting points.
“Spatial API” is a broad term for interfaces involving three-dimensional content, device tracking, environmental geometry, or scene understanding. Those are different responsibilities. Our guides help you name the layer you need before deciding how to connect it to an application.
SpatialAPI.com is an independent developer learning resource. It provides guides, official-source reading paths, and local browser demonstrations. It does not sell API keys, run a hosted spatial endpoint, or claim to operate the third-party standards and tools discussed here.
Start with a coordinate contract, clear object identity, and a small scene that loads and supports one useful interaction. Then work through model packaging and validation. The Start Here page connects the foundation articles in that order.
Begin with the task. A VR project needs a complete session and interaction journey. An AR project also needs a clear relationship between virtual content and the surrounding scene. Read the dedicated topic hubs for different planning and testing workflows.
It asks this browser whether immersive VR and AR sessions may be supported. It does not start a session, prove that every XR feature works, or validate a specific headset. The result stays in your browser and is not sent to SpatialAPI.com.
No. The articles explain architectural decisions and link to relevant official references. Vendor-specific examples are identified within their documented scope. The site is not affiliated with the standards organizations or technology providers referenced in the guides.
Start with a clear foundation. Then build the experience your audience actually needs.
Explore the developer guides