Looking Glass
Looking Glass Factory builds light field (holographic) displays — group-viewable 3D screens ranging from the pocket-sized Looking Glass Go to 16", 27", 32" and 65" panels — plus the software that drives them. For developers, the core surface is Looking Glass Bridge: a local runtime that exposes an HTTP REST API on http://localhost:33334/ for enumerating connected displays, opening the media player, building playlists of Quilt and RGBD holograms, and controlling playback. Around it Looking Glass ships official client libraries — the typesafe bridge.js (@lookingglass/bridge), a WebXR polyfill (@lookingglass/webxr) that targets the displays from any WebXR framework, a Python Bridge SDK, the legacy HoloPlay Core C/C++/C# SDK, and engine plugins for Unity, Unreal and Blender. Looking Glass Blocks (blocks.glass) hosts holograms on the internet. The company is backed by Uncork Capital and headquartered in Brooklyn, New York.
Looking Glass publishes 6 API contracts indexed on the APIs.io network, including Autostart API, Devices API, Orchestration API, and 3 more. Tagged areas include Company, Holographic Displays, Light Field, 3D, and Developer Tools.
The Looking Glass catalog on APIs.io includes 1 Spectral governance ruleset.
Looking Glass’ developer surface includes documentation, API reference, engineering blog, pricing, signup flow, authentication, and 19 more developer resources.
Kin Score
Markets this provider is in provisional
The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.
| Market | Position | Depth | Registered MCP server | Declares compatibility |
|---|---|---|---|---|
| XR & Graphics (XR, 3D, GPU graphics) | undeclared | - | - | - |
Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Standards implemented 1
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
APIs 6
Individual APIs this provider publishes, each with its own machine-readable definition.
Looking Glass Autostart API
Playlists that auto-play when Bridge starts
Looking Glass Devices API
Enumerate connected Looking Glass displays
Looking Glass Orchestration API
Multi-user Bridge sessions (orchestrations)
Looking Glass Playback API
Transport controls for the Bridge media player
Looking Glass Playlist API
Create, edit and delete hologram playlists
Looking Glass Version API
Bridge and API version information
Open Collections 6
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Looking Glass Bridge Autostart API
OPEN COLLECTIONLooking Glass Bridge Autostart Devices API
OPEN COLLECTIONLooking Glass Bridge Autostart Orchestration API
OPEN COLLECTIONLooking Glass Bridge Autostart Playback API
OPEN COLLECTIONLooking Glass Bridge Autostart Playlist API
OPEN COLLECTIONLooking Glass Bridge Autostart Version API
OPEN COLLECTIONAgent Skills 1
Packaged agent skills for driving this provider's APIs from an AI assistant.
Cast a hologram to a Looking Glass display
AGENT SKILLSpectral Rules 1
Spectral governance rulesets for linting and validating these APIs.
Looking Glass API Rules
SPECTRALOpenAPI Overlays 1
Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.
Looking Glass Bridge Overlay
DERIVEDSecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Get Started 2
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
Source (apis.yml)
Looking Glass API — frequently asked questions
Does Looking Glass have an API?
Yes. APIs.io lists 6 APIs from Looking Glass, including Looking Glass Autostart API, Looking Glass Devices API and Looking Glass Orchestration API, and 3 more.
Is there an OpenAPI specification for the Looking Glass API?
Yes. APIs.io indexes 6 OpenAPI specifications for Looking Glass, each linked for download from this page.
How do I authenticate with the Looking Glass API?
Looking Glass uses bearer-token authentication (0 schemes). The details are profiled on APIs.io as Looking Glass Authentication.
Is the Looking Glass API ready for AI agents?
Looking Glass has a Kin Score of 39.8 out of 100 (developing) and an Agent Readiness score of 18.1 (agent-aware), scored by API Evangelist on 2026-11-06.
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.