Looking Glass Factory · Authentication Profile

Looking Glass Factory Authentication

Authentication

Looking Glass Factory secures its APIs with oauth2 and none across 2 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode flow(s).

CompanyHardwareHolographic Displays3DLight FieldDeveloper ToolsSDKGraphQLWebXRAR/VR

Methods: oauth2, none Schemes: 2 OAuth flows: authorizationCode API key in:

Security Schemes

Auth0 (Blocks API) oauth2

None (Bridge local REST) none

Source

Authentication Profile

generated: '2026-07-20'
method: searched
source: https://github.com/Looking-Glass/blocks.js + https://lfdocs.lookingglassfactory.com/software/looking-glass-bridge-sdk/web-application-integration
docs: https://docs.lookingglassfactory.com/
summary:
  types: [oauth2, none]
  oauth2_flows: [authorizationCode]
  notes: >-
    Looking Glass exposes two developer APIs with distinct auth models. The
    hosted Blocks GraphQL API authenticates via Auth0 (OAuth 2.0 / OIDC,
    redirect-based authorization-code login using a per-app Client ID). The
    local Bridge HTTP REST API is served by the Looking Glass Bridge desktop
    runtime on localhost and requires no network credential (loopback-only).
schemes:
  - name: Auth0 (Blocks API)
    type: oauth2
    flow: authorizationCode
    provider: Auth0
    applies_to: Blocks GraphQL API (https://blocks.glass/api/graphql)
    detail: >-
      "Blocks uses Auth0 under the hood for authentication." Developers request
      a Client ID via form; blocks.js runs the OAuth redirect login and attaches
      the resulting bearer token to GraphQL requests.
    source: https://github.com/Looking-Glass/blocks.js
  - name: None (Bridge local REST)
    type: none
    applies_to: Bridge HTTP REST API (localhost media-player control)
    detail: >-
      The Bridge REST API is exposed by the locally-installed Looking Glass
      Bridge runtime over loopback; it controls the local media player and
      carries no authentication.
    source: https://lfdocs.lookingglassfactory.com/software/looking-glass-bridge-sdk/web-application-integration

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this

find_securityBrowse and filter every security artifact in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This security artifact

curl "https://apis.io/api/v1/security/looking-glass-factory-authentication"

All security posture

curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.