Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
8th Wall website screenshot

8th Wall

8th Wall is a web-based augmented reality (WebAR) platform originally founded in 2016 and acquired by Niantic in March 2022. Following Niantic's 2025 sale of its gaming division to Scopely and the spin-off of Niantic Spatial, Inc. as an independent geospatial AI and XR company, 8th Wall's hosted cloud editor, login, and Niantic Studio services were retired on February 28, 2026 and the platform transitioned to a free, open-source distribution model. Existing published 8th Wall experiences continue to run through February 28, 2027. The 8th Wall stack centers on the XR Engine — a SLAM-based WebAR runtime providing World Tracking, Image Targets, Face Effects, Sky Segmentation, and World Effects — exposed to developers as a TypeScript/JavaScript SDK that integrates with A-Frame, three.js, PlayCanvas, and Babylon.js. The Distributed Engine Binary (released January 2026) ships SLAM under a binary-only license for commercial and noncommercial use, while the surrounding framework, utilities, and example projects are MIT-licensed on the 8thwall GitHub organization. 8th Wall Studio (formerly Niantic Studio) is a real-time visual editor and game engine for authoring 3D and XR experiences that can be deployed to any web host. 8th Wall does not publish a public REST or HTTP API; the developer surface is a client-side JavaScript SDK plus command-line and utility tooling distributed through GitHub.

human only

Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.

Kin Score

API Evangelist profiles 8th Wall the way a machine reads it — 1 machine-readable artifact, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.

Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — 8th Wall scores 11.8/100 (minimal), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 11.8/100 · minimal
Contract Quality 0.0 / 25
Developer Ergonomics 4.3 / 20
Commercial Clarity 0.0 / 20
Operational Transparency 0.7 / 13
Governance 0.0 / 12
Discoverability 6.8 / 10
Agent readiness — 0/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile 8th Wall

Each block below is one kind of artifact we hold for 8th Wall. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

Security Posture 1

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Niantic 8Thwall Domain Security

TLSv1.3 · DMARC

SECURITY

Resources

Every other property we hold for 8th Wall — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

Get Started 1

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 1

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Commercial 1

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

← All providers · Data indexed from github.com/api-evangelist/niantic-8thwall · machine-readable index on apis.io