Lumos

Lumos is the first Autonomous Identity Platform that helps organizations discover and manage access to all apps with enhanced security, increased productivity, and reduced cost. Lumos automates access requests, enforces least privilege, speeds up user access reviews, and eliminates extra SaaS app spending through 80+ connectors and an API.

Lumos publishes 10 API contracts indexed on the APIs.io network, including Tasks API, Access Reviews API, Core API, and 7 more. Tagged areas include Identity and Access Management, Access Reviews, Deprovisioning, Identity Governance, and Identity Platform.

The Lumos catalog on APIs.io includes 1 event-driven AsyncAPI specification and 1 Spectral governance ruleset.

Lumos’ developer surface includes authentication, documentation, support, getting-started guide, engineering blog, signup flow, CLI, and 37 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

62.9/100 strong ▬ flat Agent 60/100 agent ready Front door AI 6/6 dominant Heartbeat 92/100 alive saas Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →

AccessEnterprise

2 published contracts 1 MCP Servers 4 Agent Skills

Identity and Access Management Access ReviewsDeprovisioningIdentity GovernanceIdentity PlatformLeast Privilege Provisioning SaaS Management Shadow IT

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Cybersecurity Management

BC-620

Access ReviewsApp StoreCoreLifecycle Management

POST /access_reviews POST /appstore/requestable_permissions POST /appstore/pre_approval_rules POST /lifecycle-management/user-offboardings

Kin Score

Kin Score How this is scored →
scored 2026-11-13 · rubric v0.28.0

Composite quality — 62.9/100 · strong

Contract Quality 12.4 / 19

Developer Ergonomics 11.0 / 15

Access Clarity 6.4 / 15

Operational Transparency 5.8 / 10

Contract Governance 2.9 / 9

Discoverability 5.6 / 8

Regulatory Posture 4.4 / 15

Create-or-Update Ergonomics 2.8 / 10

Agent readiness — 60/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 6 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 6 / 6

Protected Resource Metadata 5 / 5

Registration Without a Human 6 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/lumos/"><img src="https://apis.io/badge/lumos/card.svg" alt="Lumos on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented) Ask about this →
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0 Ask about this →
Agentic Commerce Well-Known Document +5 pts — a parsing /.well-known/ucp.json or acp.json declaring a version and at least one service, OR (0.27) a live x402 payment challenge from _data/x402-adoption.json — `self` when its endpoints are on the provider's own domain, `platform` when they are on a vendor's Ask about this →
Dry-Run / Simulate Mode +4 pts — OpenAPI: destructive operations expose a dry_run / simulate / preview / validate_only parameter Ask about this →
Well-Known Catalog +4 pts — common[].type includes WellKnown, APICatalog, or api-catalog Ask about this →
Consent & Bot Identity +3 pts — common[].type includes AIPREF, ContentSignal, WebBotAuth, or HTTPMessageSignatures Ask about this →

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 42.6 — up to +11.5 composite points Ask about this →
Contract Quality scores 66.0 — up to +8.5 composite points Ask about this →
Contract Governance scores 31.8 — up to +8.2 composite points Ask about this →

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/lumos/apis.yml: open an issue on github.com/api-evangelist/lumos to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

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
Atlassian Marketplace (builders on Jira, Confluence, Bitbucket)	builds-on	51.8	-	-

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 6

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.

IAM

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

Model Context Protocol (MCP)

measured — observed by APIs.io (verified)

OAuth 2.0 Protected Resource Metadata

measured — observed by APIs.io (verified)

Dynamic Client Registration

measured — observed by APIs.io (published)

OpenAPI

measured — observed by APIs.io (published)

OAuth 2.0

measured — observed by APIs.io (declared)

APIs 10

Individual APIs this provider publishes, each with its own machine-readable definition.

Lumos Connector SDK

The Lumos Connector SDK allows developers to build custom connectors that integrate third-party applications with the Lumos platform, enabling automated provisioning, deprovisio...

Lumos Tasks API

The Tasks API from Lumos — 8 operation(s) for tasks.

Lumos Access Reviews API

Create and manage access review campaigns — scheduled reviews of who has access to what across your connected apps. **Typical workflow for creating a review:** 1. `GET /apps` — ...

Lumos Core API

The Core API from Lumos — 27 operation(s) for core.

Lumos Integration Webhooks API

The Integration Webhooks API from Lumos — 2 operation(s) for integration webhooks.

Lumos Knowledge API

Knowledge entries are the documents and notes Lumos agents draw on when they answer access questions. Each entry carries a title, body, tags, and product scopes, plus an optiona...

Lumos Lifecycle Management API

The Lifecycle Management API from Lumos — 3 operation(s) for lifecycle management.

Lumos Meta API

The Meta API from Lumos — 2 operation(s) for meta.

Lumos Vendor Management API

The Vendor Management API from Lumos — 4 operation(s) for vendor management.

Lumos App Store API

The App Store API from Lumos — 11 operation(s) for app store.

Scroll for all 10

Open Collections 14

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Lumos REST AccessPolicies API

OPEN COLLECTION

Lumos REST AccessPolicies AccessRequests API

OPEN COLLECTION

Lumos REST AccessPolicies Accounts API

OPEN COLLECTION

Lumos REST AccessPolicies Activity API

OPEN COLLECTION

Lumos REST AccessPolicies Apps API

OPEN COLLECTION

Lumos REST AccessPolicies AppStore API

OPEN COLLECTION

Lumos REST AccessPolicies Groups API

OPEN COLLECTION

Lumos REST AccessPolicies PreApprovalRules API

OPEN COLLECTION

Lumos REST AccessPolicies Tasks API

OPEN COLLECTION

Lumos REST AccessPolicies Users API

OPEN COLLECTION

Lumos REST AccessPolicies Utility API

OPEN COLLECTION

Lumos REST AccessPolicies Vendors API

OPEN COLLECTION

Lumos REST AccessPolicies Webhooks API

OPEN COLLECTION

Lumos REST API

OPEN COLLECTION

Scroll for all 14

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Lumos MCP

Lumos ships TWO first-party remote MCP servers on its own API host: an end-user server for self-service access requests, and an admin server whose tools are selected per-connect...

MCP SERVER

Agent Skills 4

Packaged agent skills for driving this provider's APIs from an AI assistant.

lumos-clear-task-queue

AGENT SKILL

lumos-offboard-user

AGENT SKILL

lumos-request-access

AGENT SKILL

lumos-run-access-review

AGENT SKILL

Lumos API pricing

Rate limits

Unauthenticated edge limit (observed): 10 not stated

Rate-limit details →

Pricing Plans 1

Published pricing tiers and plan structures.

Lumos Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Lumos Rate Limits

1 limits

RATE LIMITS

Privacy & Data 1

Its role, the data it processes, retention and transfers, quoted from its own privacy page.

Lumos

19 quoted statements, read from Lumos's own page on 2026-11-10.

PRIVACY

Compliance 1

Attestations the provider states (SOC 2, ISO 27001 and others), quoted from its own trust page. APIs.io verifies none of them.

Lumos

3 quoted statements, read from Lumos's own page on 2026-11-10.

COMPLIANCE

FinOps 1

Cost, billing, and metering signals for API financial operations.

Lumos Finops

FINOPS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Lumos Webhooks

ASYNCAPI

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs. Counts are the severity each rule declares, not results of running them.

Lumos API Rules

54 rules · 42 error-severity 10 warn-severity 2 info-severity

SPECTRAL

OpenAPI 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.

Lumos Openapi Overlay

9 actions · documentation

GENERATED

Security Posture 3

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

Lumos Authentication

http/oauth2 · 2 schemes

SECURITY

Lumos Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Lumos Trust Center

trust center published

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Lumos Scopes

14 scopes · authorization_code

14 scopes

SCOPES

Agentic Access (API Evangelist recommendations) 1

Recommended x-agentic-access execution contracts for AI agents.

Lumos Agentic Access

89 operations · 44 acting

AGENTIC

Resources

Get Started 4

Portal, sign-up, and the first successful call

GettingStarted

GettingStarted

Login

Signup

Signup

DeveloperPortal

DeveloperPortal

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 6

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

LlmsText

MCPServer

WellKnown

AgentSkill

LLMsTxt

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

DataModel

Lifecycle

Conformance

Webhooks

Build 6

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

CLI

ToolCrosswalk

Packages

SDKs

CLI

Access & Security 4

Authentication, authorization, and security posture

DomainSecurity

Authentication

TrustCenter

OAuthScopes

Operate 5

Status, limits, changes, and where to get help

Support

Roadmap

StatusPage

ChangeLog

RateLimits

Commercial 4

Pricing, plans, and the legal terms of use

Pricing

PrivacyPolicy

Plans

FinOps

Company 3

The organization behind the API

Website

Website

Blog

Blog

LinkedIn

Other 4

Properties that don't map to a standard resource type

CapabilityMap

Overlay

DataProcessing

Attestations

Source (apis.yml)

aid: lumos
name: Lumos
description: Lumos is the first Autonomous Identity Platform that helps organizations discover and manage access to all apps
  with enhanced security, increased productivity, and reduced cost. Lumos automates access requests, enforces least privilege,
  speeds up user access reviews, and eliminates extra SaaS app spending through 80+ connectors and an API.
type: Index
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: enterprise
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Enterprise
  confidence: medium
  source:
  - authentication
  - scopes
  - rate-limits
  - security
  generated: '2026-11-13'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/lumos.png
x-docs-platform: readme
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-10-03
tags:
- Identity and Access Management
- Access Reviews
- Deprovisioning
- Identity Governance
- Identity Platform
- Least Privilege
- Provisioning
- SaaS Management
- Shadow IT
tags_raw:
- Access Management
- Access Reviews
- Deprovisioning
- Identity Governance
- Identity Platform
- Least Privilege
- Provisioning
- SaaS Management
- Shadow IT
url: https://raw.githubusercontent.com/api-evangelist/lumos/refs/heads/main/apis.yml
created: '2026-03-16'
modified: '2026-08-29'
specificationVersion: '0.23'
apis:
- aid: lumos:connector-sdk
  name: Lumos Connector SDK
  description: The Lumos Connector SDK allows developers to build custom connectors that integrate third-party applications
    with the Lumos platform, enabling automated provisioning, deprovisioning, and access management for apps not yet supported
    natively.
  humanURL: https://developers.lumos.com/docs/connector-sdk
  baseURL: https://api.lumos.com
  tags:
  - Connectors
  - Integration
  - SDK
  tags_raw:
  - Connectors
  - Integrations
  - SDK
  properties:
  - url: https://developers.lumos.com/docs/connector-sdk
    type: Documentation
  - url: https://developers.lumos.com/docs/building-a-lumos-connector-step-by-step-tutorial
    type: GettingStarted
- aid: lumos:lumos-tasks-api
  name: Lumos Tasks API
  description: The Tasks API from Lumos — 8 operation(s) for tasks.
  humanURL: https://developers.lumos.com/docs/rest-api
  baseURL: https://api.lumos.com
  tags:
  - Task
  tags_raw:
  - Tasks
  properties:
  - type: OpenAPI
    url: openapi/lumos-tasks-api-openapi.yml
- aid: lumos:lumos-access-reviews-api
  name: Lumos Access Reviews API
  description: "Create and manage access review campaigns — scheduled reviews of who has access to what\nacross your connected\
    \ apps.\n\n**Typical workflow for creating a review:**\n\n1. `GET /apps` — find the domain app UUIDs you want to review.\n\
    2. `GET /access_reviews/scope_options?domain_app_id={id}` — discover available scope\n   filters (employment status, team,\
    \ last login, etc.). Each returned `items` entry is a\n   ready-to-POST `scope_filters` payload; datetime and custom-attribute\
    \ groups instead\n   expose a `filter_input_template`.\n3. `POST /access_reviews` with `apps` (optionally with `scope_filters`\
    \ per app) —\n   creates the campaign.\n4. `GET /access_reviews/{id}` — poll until `status` transitions from `IN_PREPARATION`\n\
    \   to `IN_PROGRESS`.\n\n**After creation:**\n\n- `POST /access_reviews/{id}/apps` — add more apps while `status != COMPLETED`.\n\
    - `PATCH /access_reviews/{id}` — update name / deadline / owner, or per-ARDA\n  `scope_filters` and removal action.\n\
    - `DELETE /access_reviews/{id}` — soft-delete the whole campaign.\n- `DELETE /access_reviews/{id}/apps/{arda_id}` — soft-delete\
    \ a single app from the\n  campaign.\n\nAll endpoints require an API token with the `access_reviews.create` or\n`access_reviews.view`\
    \ permission (Access Review Administrator or App Admin role)."
  humanURL: https://developers.lumos.com/docs/rest-api
  baseURL: https://api.lumos.com
  tags:
  - Access Reviews
  properties:
  - type: OpenAPI
    url: openapi/lumos-access-reviews-api-openapi.yml
  - type: Documentation
    url: https://developers.lumos.com/reference/lumos-api
  - type: GettingStarted
    url: https://developers.lumos.com/docs/quick-start
  - type: Authentication
    url: https://developers.lumos.com/docs/rest-api
- aid: lumos:lumos-core-api
  name: Lumos Core API
  description: The Core API from Lumos — 27 operation(s) for core.
  humanURL: https://developers.lumos.com/docs/rest-api
  baseURL: https://api.lumos.com
  tags:
  - Core
  properties:
  - type: OpenAPI
    url: openapi/lumos-core-api-openapi.yml
  - type: Documentation
    url: https://developers.lumos.com/reference/lumos-api
  - type: GettingStarted
    url: https://developers.lumos.com/docs/quick-start
  - type: Authentication
    url: https://developers.lumos.com/docs/rest-api
- aid: lumos:lumos-integration-webhooks-api
  name: Lumos Integration Webhooks API
  description: The Integration Webhooks API from Lumos — 2 operation(s) for integration webhooks.
  humanURL: https://developers.lumos.com/docs/rest-api
  baseURL: https://api.lumos.com
  tags:
  - Integration Webhooks
  properties:
  - type: OpenAPI
    url: openapi/lumos-integration-webhooks-api-openapi.yml
  - type: Documentation
    url: https://developers.lumos.com/reference/lumos-api
  - type: GettingStarted
    url: https://developers.lumos.com/docs/quick-start
  - type: Authentication
    url: https://developers.lumos.com/docs/rest-api
- aid: lumos:lumos-knowledge-api
  name: Lumos Knowledge API
  description: 'Knowledge entries are the documents and notes Lumos agents draw on when they answer access

    questions. Each entry carries a title, body, tags, and product scopes, plus an optional file

    attachment.


    Because of that attachment, create and update send `multipart/form-data` rather than JSON. On

    update, tag and scope lists replace what was there instead of appending, and `clear_attachment=true`

    removes an existing file without uploading a replacement.


    `DELETE` archives rather than destroys. The entry stops appearing in list results and stays

    recoverable.


    Pages here are small: `page_size` defaults to 10 and is clamped to 25.'
  humanURL: https://developers.lumos.com/docs/rest-api
  baseURL: https://api.lumos.com
  tags:
  - Knowledge
  properties:
  - type: OpenAPI
    url: openapi/lumos-knowledge-api-openapi.yml
  - type: Documentation
    url: https://developers.lumos.com/reference/lumos-api
  - type: GettingStarted
    url: https://developers.lumos.com/docs/quick-start
  - type: Authentication
    url: https://developers.lumos.com/docs/rest-api
- aid: lumos:lumos-lifecycle-management-api
  name: Lumos Lifecycle Management API
  description: The Lifecycle Management API from Lumos — 3 operation(s) for lifecycle management.
  humanURL: https://developers.lumos.com/docs/rest-api
  baseURL: https://api.lumos.com
  tags:
  - Lifecycle Management
  properties:
  - type: OpenAPI
    url: openapi/lumos-lifecycle-management-api-openapi.yml
  - type: Documentation
    url: https://developers.lumos.com/reference/lumos-api
  - type: GettingStarted
    url: https://developers.lumos.com/docs/quick-start
  - type: Authentication
    url: https://developers.lumos.com/docs/rest-api
- aid: lumos:lumos-meta-api
  name: Lumos Meta API
  description: The Meta API from Lumos — 2 operation(s) for meta.
  humanURL: https://developers.lumos.com/docs/rest-api
  baseURL: https://api.lumos.com
  tags:
  - Meta
  properties:
  - type: OpenAPI
    url: openapi/lumos-meta-api-openapi.yml
  - type: Documentation
    url: https://developers.lumos.com/reference/lumos-api
  - type: GettingStarted
    url: https://developers.lumos.com/docs/quick-start
  - type: Authentication
    url: https://developers.lumos.com/docs/rest-api
- aid: lumos:lumos-vendor-management-api
  name: Lumos Vendor Management API
  description: The Vendor Management API from Lumos — 4 operation(s) for vendor management.
  humanURL: https://developers.lumos.com/docs/rest-api
  baseURL: https://api.lumos.com
  tags:
  - Vendor Management
  properties:
  - type: OpenAPI
    url: openapi/lumos-vendor-management-api-openapi.yml
  - type: Documentation
    url: https://developers.lumos.com/reference/lumos-api
  - type: GettingStarted
    url: https://developers.lumos.com/docs/quick-start
  - type: Authentication
    url: https://developers.lumos.com/docs/rest-api
- aid: lumos:lumos-app-store-api
  name: Lumos App Store API
  description: The App Store API from Lumos — 11 operation(s) for app store.
  humanURL: https://developers.lumos.com/docs/connector-sdk
  baseURL: https://api.lumos.com
  tags:
  - App Store
  properties:
  - type: OpenAPI
    url: openapi/lumos-app-store-api-openapi.yml
common:
- type: CapabilityMap
  url: capabilities/lumos-capability-edges.yml
  name: Lumos Business Capability Map
- type: AgenticAccess
  url: agentic-access/lumos-agentic-access.yml
- type: DomainSecurity
  url: security/lumos-domain-security.yml
- type: Authentication
  url: authentication/lumos-authentication.yml
- type: Website
  url: https://www.lumos.com/
- type: Documentation
  url: https://developers.lumos.com/
- type: Support
  url: https://support.lumos.com/
- type: GettingStarted
  url: https://developers.lumos.com/docs/getting-started
- type: Blog
  url: https://www.lumos.com/blog
- type: Login
  url: https://app.lumosidentity.com/
- type: Signup
  url: https://www.lumos.com/demo
- type: GitHubOrganization
  url: https://github.com/teamlumos
- type: LinkedIn
  url: https://www.linkedin.com/company/lumosidentity
- type: CLI
  url: https://developers.lumos.com/docs/cli
- type: Integrations
  url: https://www.lumos.com/integrations
- type: LlmsText
  url: https://developers.lumos.com/llms.txt
- type: DeveloperPortal
  url: https://developers.lumos.com/
- type: APIReference
  url: https://developers.lumos.com/reference/lumos-api
- type: Roadmap
  url: https://developers.lumos.com/page/public-roadmap
- type: Pricing
  url: https://www.lumos.com/pricing
- type: PrivacyPolicy
  url: https://www.lumos.com/privacy
- type: StatusPage
  url: https://status.lumos.com/
- type: TrustCenter
  url: https://trust.lumos.com/
- type: MCPServer
  url: mcp/lumos-mcp.yml
- type: ToolCrosswalk
  url: mcp/lumos-tool-crosswalk.yml
- type: OAuthScopes
  url: scopes/lumos-scopes.yml
- type: WellKnown
  url: well-known/lumos-well-known.yml
- type: Packages
  url: packages/lumos-packages.yml
- type: SDKs
  url: packages/lumos-packages.yml
- type: CLI
  url: cli/lumos-cli.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Conventions
  url: conventions/lumos-conventions.yml
- type: ErrorCatalog
  url: errors/lumos-error-codes.yml
- type: DataModel
  url: data-model/lumos-data-model.yml
- type: Lifecycle
  url: lifecycle/lumos-lifecycle.yml
- type: ChangeLog
  url: changelog/lumos-changelog.yml
- type: Conformance
  url: conformance/lumos-conformance.yml
- type: Webhooks
  url: asyncapi/lumos-webhooks.yml
- type: Overlay
  url: overlays/lumos-openapi-overlay.yaml
- type: LLMsTxt
  url: llms/lumos-llms.txt
- type: RateLimits
  url: rate-limits/lumos-rate-limits.yml
- type: Plans
  url: plans/lumos-plans-pricing.yml
- type: FinOps
  url: finops/lumos-finops.yml
- type: DataProcessing
  url: privacy/lumos-privacy-policy.yml
- type: Attestations
  url: compliance/lumos-compliance.yml
integrations:
- name: websights
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
x-enrichment:
  date: '2026-08-29'
  status: enriched
  artifacts_added: 24
  pass: local-v1

Lumos API — frequently asked questions

Does Lumos have an API?

Yes. APIs.io lists 10 APIs from Lumos, including Lumos Connector SDK, Lumos Tasks API and Lumos Access Reviews API, and 7 more.

Is there an OpenAPI specification for the Lumos API?

Yes. APIs.io indexes 9 OpenAPI specifications for Lumos, each linked for download from this page.

How do I authenticate with the Lumos API?

Lumos documents its authentication (http/oauth2 · 2 schemes). The details are profiled on APIs.io as Lumos Authentication.

Does Lumos have an MCP server?

Yes. APIs.io lists 1 MCP server for Lumos: Lumos ships TWO first-party remote MCP servers on its own API host: an end-user server for self-service access requests, and an admin server whose tools are selected per-connection through a `toolsets

Is the Lumos API ready for AI agents?

Lumos has a Kin Score of 62.9 out of 100 (strong) and an Agent Readiness score of 60.3 (agent-ready), scored by API Evangelist on 2026-11-13.

Work with this as data

Every provider 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 providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
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 provider

curl "https://apis.io/api/v1/providers/lumos"

All providers

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

Every operation they expose

curl "https://apis.io/api/v1/providers/lumos/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/lumos/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.