Lumos · Authentication Profile

Lumos Authentication

Authentication

Lumos runs TWO independent credential systems on one host. The REST API takes a static bearer API key prefixed `lsk_`. The two hosted MCP servers take an OAuth 2.1 access token from b.app.lumosidentity.com and explicitly refuse API keys. An agent that has a working REST key still cannot call the MCP servers, and vice versa.

Lumos secures its APIs with http and oauth2 across 2 declared security schemes, as derived from its OpenAPI definitions.

Access ManagementAccess ReviewsDeprovisioningIdentity GovernanceIdentity PlatformLeast PrivilegeProvisioningSaaS ManagementShadow IT
Methods: http, oauth2 Schemes: 2 OAuth flows: API key in:

Security Schemes

HTTPBearer http
scheme: bearer · in: Authorization header ()
LumosOAuth oauth2
· flows:

Source

Authentication Profile

Raw ↑ 
generated: '2026-08-29'
method: searched
source: >-
  https://developers.lumos.com/docs/rest-api, https://api.lumos.com/openapi.json,
  https://api.lumos.com/.well-known/oauth-authorization-server, and the RFC 9728 protected-resource
  documents for both MCP endpoints
docs: https://developers.lumos.com/docs/rest-api
description: >-
  Lumos runs TWO independent credential systems on one host. The REST API takes a static bearer API
  key prefixed `lsk_`. The two hosted MCP servers take an OAuth 2.1 access token from
  b.app.lumosidentity.com and explicitly refuse API keys. An agent that has a working REST key still
  cannot call the MCP servers, and vice versa.
summary:
  types:
  - http
  - oauth2
  systems: 2
schemes:
- name: HTTPBearer
  type: http
  scheme: bearer
  bearerFormat: Lumos API key (lsk_ prefix)
  applies_to: REST API (https://api.lumos.com)
  in: Authorization header
  key_prefix: lsk_
  rotation: not documented
  expiry: not documented
  sources:
  - openapi/lumos-openapi.json
  - https://developers.lumos.com/docs/rest-api
- name: LumosOAuth
  type: oauth2
  applies_to:
  - https://api.lumos.com/mcp/user
  - https://api.lumos.com/mcp/admin
  flows:
    authorizationCode:
      authorizationUrl: https://b.app.lumosidentity.com/b/oauth/authorize
      tokenUrl: https://b.app.lumosidentity.com/b/oauth/token
      refreshUrl: https://b.app.lumosidentity.com/b/oauth/token
      pkce: S256
  issuer: https://b.app.lumosidentity.com
  dynamic_client_registration: https://b.app.lumosidentity.com/b/oauth/register
  token_endpoint_auth_methods:
  - none
  - client_secret_basic
  - client_secret_post
  scopes: scopes/lumos-scopes.yml
  discovery:
  - https://api.lumos.com/.well-known/oauth-authorization-server
  - https://api.lumos.com/.well-known/oauth-protected-resource/mcp/user
  - https://api.lumos.com/.well-known/oauth-protected-resource/mcp/admin
  sources:
  - well-known/lumos-oauth-authorization-server.json
  - https://developers.lumos.com/docs/mcp
  note: >-
    Public-client friendly — `none` is an accepted token endpoint auth method and RFC 7591 dynamic
    registration is open, which is what lets an arbitrary MCP client onboard without a pre-provisioned
    client_id.
challenge_observed:
  url: https://api.lumos.com/mcp/user
  http_status: 401
  www_authenticate: Bearer resource_metadata="https://api.lumos.com/.well-known/oauth-protected-resource/mcp/user"
  probed: '2026-08-29'

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/lumos-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.