# Lumos Helmet

**Canonical:** https://apis.io/providers/lumos-helmet/  
**Website:** https://lumoshelmet.co/  
**APIs profiled:** 0

Lumos (Lumos Helmet) is a consumer hardware company that designs and manufactures smart bike helmets and connected bike lights with integrated safety features such as turn signals, brake lights, and high-visibility LED lighting. Its product line spans commuter, e-bike, and kids' helmets plus standalone smart bike lights, controlled through companion iOS and Android mobile apps. Backed by Techstars, Lumos sells direct-to-consumer through an online store; it does not currently publish a public API, developer platform, or SDK. This profile was enriched by the API Evangelist pipeline, which confirmed no programmatic API surface and captured the company's identity and domain-security posture.

## Kin Score — 10.2 / 100 (minimal)

Scored 2026-08-20 under rubric 0.12.0. Trend: flat (+0.0 from 10.2).

| Facet | Score |
|---|---|
| Discoverability | 50.0 |
| Contract Quality | 0.0 |
| Governance | 0.0 |
| Contract Governance | 0.0 |
| Operational Transparency | 0.0 |
| Developer Ergonomics | 4.8 |
| Commercial Clarity | 21.1 |
| Access Clarity | 21.1 |

## Agent readiness — 0.0 (human-only)

| Dimension | Value |
|---|---|
| Spec Presence | no |
| Agentic Access | no |
| Reversibility Documented | no |
| MCP Server | no |
| Auth Clarity | no |
| Idempotency | no |
| Error Semantics | no |
| OpenAPI Examples | no |
| Rate Limit Signal | no |
| Event Surface Described | no |
| Agent Skills | no |
| Well Known Catalog | no |
| Consent Identity | no |
| Agent Card | no |
| Dry Run Mode | no |

## Access

Unknown — onboarding: unknown, pricing: unknown, trial: no (confidence: low).

## Security (1)

- **Lumos Helmet Domain Security** — TLSv1.3 · HSTS · DNSSEC · DMARC

## Tags

Company, Consumer Hardware, Wearables, Cycling, Bike Safety, Smart Helmets, IoT, Mobile Apps

---

Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/providers/lumos-helmet/). Scores are computed from the provider's own public artifacts under a published rubric.
