Lumotive

Lumotive is a Seattle-based semiconductor company building programmable optics on its patented Light Control Metasurface (LCM) technology — solid-state, software-defined beam steering implemented in a standard CMOS process with no moving parts. Its products include the LM10 and LX10 LCM beam-steering chips, the LCM Evaluation Kit (LEK), the M30 iToF and NM120 3D-sensing development kits, and the M30/TX10 reference designs, applied to industrial automation, intelligent traffic systems, automotive ADAS and autonomy, defense, and optical circuit switching for AI data centers. Lumotive publishes an "Open Lidar API" — a real-time control interface for software-defined Lidar 2.0 hardware covering region-of-interest scanning, frame rate, resolution and range, plus a common point-cloud format — and ships C/C++ LCM control libraries with Python bindings alongside its evaluation kits. That interface is an embedded hardware-control API, not a public web API: no developer portal, documentation site, machine-readable specification, or self-service sign-up is published, and access is granted to selected partners through the Technology Access Program by contacting the company.

Lumotive is profiled on the APIs.io network. Tagged areas include Company, Semiconductors, Photonics, LiDAR, and 3D Sensing.

Lumotive’s developer surface includes engineering blog, support, and 7 more developer resources.

🌐 Visit website 📡 Source on GitHub

9.6/100 minimal ▬ flat Agent 3/100 human only saas Full breakdown ↓
scored 2026-09-02 · rubric v0.18.0

0 APIs

Company Semiconductors Photonics LiDAR 3D SensingProgrammable OpticsBeam SteeringRobotics Automotive Industrial Automation Defense Optical Networking Hardware

Kin Score

Kin Score How this is scored →
scored 2026-09-02 · rubric v0.18.0

Composite quality — 9.6/100 · minimal

Contract Quality 0.0 / 25

Developer Ergonomics 1.4 / 20

Access Clarity 2.1 / 20

Operational Transparency 0.3 / 13

Contract Governance 0.0 / 12

Discoverability 5.7 / 10

Agent readiness — 3/100 · human only

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 0 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 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 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Surface 0 / 5

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 github.com/api-evangelist/lumotive: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Pricing Plans 1

Published pricing tiers and plan structures.

Lumotive Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Access & Security 1

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Operate 1

Status, limits, changes, and where to get help

Support

Support

Commercial 2

Pricing, plans, and the legal terms of use

PrivacyPolicy

PrivacyPolicy

Plans

Plans

Company 3

The organization behind the API

Website

Website

Blog

Blog

BlogRSS

BlogRSS

Source (apis.yml)

aid: lumotive
name: Lumotive
description: 'Lumotive is a Seattle-based semiconductor company building programmable optics on its patented Light Control
  Metasurface (LCM) technology — solid-state, software-defined beam steering implemented in a standard CMOS process with no
  moving parts. Its products include the LM10 and LX10 LCM beam-steering chips, the LCM Evaluation Kit (LEK), the M30 iToF
  and NM120 3D-sensing development kits, and the M30/TX10 reference designs, applied to industrial automation, intelligent
  traffic systems, automotive ADAS and autonomy, defense, and optical circuit switching for AI data centers. Lumotive publishes
  an "Open Lidar API" — a real-time control interface for software-defined Lidar 2.0 hardware covering region-of-interest
  scanning, frame rate, resolution and range, plus a common point-cloud format — and ships C/C++ LCM control libraries with
  Python bindings alongside its evaluation kits. That interface is an embedded hardware-control API, not a public web API:
  no developer portal, documentation site, machine-readable specification, or self-service sign-up is published, and access
  is granted to selected partners through the Technology Access Program by contacting the company.'
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - rate-limits
  - security
  generated: '2026-09-02'
  method: derived
image: https://lumotive.com/wp-content/uploads/2024/10/LM10-chip-1024x787.png
url: https://raw.githubusercontent.com/api-evangelist/lumotive/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
x-tier: stub
x-tier-reason: harvest
specificationVersion: '0.20'
created: '2026-08-25'
modified: '2026-08-25'
tags:
- Company
- Semiconductors
- Photonics
- LiDAR
- 3D Sensing
- Programmable Optics
- Beam Steering
- Robotics
- Automotive
- Industrial Automation
- Defense
- Optical Networking
- Hardware
tags_raw:
- Company
- Semiconductors
- Photonics
- Lidar
- 3D Sensing
- Programmable Optics
- Beam Steering
- Robotics
- Automotive
- Industrial Automation
- Defense
- Optical Networking
- Hardware
apis: []
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: DomainSecurity
  url: security/lumotive-domain-security.yml
- type: Website
  url: https://lumotive.com/
- type: Blog
  url: https://lumotive.com/news/
- type: BlogRSS
  url: https://lumotive.com/feed/
- type: PrivacyPolicy
  url: https://lumotive.com/privacy-policy/
- type: Support
  url: https://lumotive.com/contact/
- type: GitHubOrganization
  url: https://github.com/lumotive
- type: LLMsTxt
  url: llms/lumotive-llms.txt
- type: Plans
  url: plans/lumotive-plans-pricing.yml
x-enrichment:
  date: '2026-08-25'
  status: minimal
  artifacts_added: 6
  pass: local-v1
x-coverage:
  state: gated
  reason: sales-gate
  detail: Lumotive markets an "Open Lidar API" for software-defined lidar, but its own announcement says the API "and its
    supporting hardware platform are available now to selected partners by contacting Lumotive" — the C/C++ control libraries
    and Python bindings ship only inside the LCM Evaluation Kit, and lumotive.com serves no developer, docs or API-reference
    page at all (none appears in its own page sitemap).
  evidence:
  - url: https://lumotive.com/press-releases/lumotive-introduces-open-lidar-api-to-accelerate-market-adoption-of-software-defined-solid-state-lidar-2-0-solutions/
    status: 200
  - url: https://lumotive.com/products/lek/
    status: 200
  - url: https://lumotive.com/developers/
    status: 404
  - url: https://lumotive.com/docs/
    status: 404
  - url: https://lumotive.com/openapi.json
    status: 404
  - url: https://lumotive.com/.well-known/agent-card.json
    status: 404
  checked: '2026-08-25'

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/lumotive"

All providers

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

Every operation they expose

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

How their score was established

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

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

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

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