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 APIs 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.
Looking Glass’ developer surface includes documentation, API reference, engineering blog, pricing, signup flow, authentication, and 18 more developer resources.
Kin Score
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
MCP Servers 1
Model Context Protocol servers that expose these APIs to AI agents.
looking-glass-mcp.yml
MCP SERVERSecurity 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 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type