Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Lighthouse website screenshot

Lighthouse

Lighthouse is an UNRESOLVED venture-portfolio lead in the API Evangelist network: the slug conflates at least two different companies named "Lighthouse" surfaced by two different VC portfolio harvests, and neither resolves to a live company with a developer surface. Accel lists Lighthouse as a seed-stage "metaverse search engine" at www.lighthouselabs.xyz — that domain now serves a GoDaddy/Afternic domain-for-sale parking lander (registered 2026-04-06, nameservers ns5/ns6.afternic.com), so the company appears defunct or renamed. DCM Ventures lists Lighthouse as an "AI meeting notes and productivity app" at lighthouse.app — that domain resolves 200 but serves an unrelated Texas apartment-rental cash-back platform transitioning to the UMoveFree brand, with no developer portal, no API, and no docs. The established hospitality/travel-intelligence company also named Lighthouse (formerly OTA Insight) is already profiled separately in the network as the lighthouse-travel provider and is NOT this record. Enrichment is blocked pending a human decision on which entity, if any, this slug should represent.

human only

Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.

Kin Score

Lighthouse is tracked in the API Evangelist network. This page is the human-readable profile that sits on top of the machine-readable index we maintain at apis.io.

Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Lighthouse scores 6.8/100 (minimal), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 6.8/100 · minimal
Contract Quality 0.0 / 25
Developer Ergonomics 0.0 / 20
Commercial Clarity 0.0 / 20
Operational Transparency 0.0 / 13
Governance 0.0 / 12
Discoverability 6.8 / 10
Agent readiness — 0/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
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 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

Resources

Every other property we hold for Lighthouse — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

Company 1

The organization behind the API

Lighthouse is in the network as a tracked entity. We haven't yet indexed a public API surface for it — when one is published, the artifacts, score, and agent-readiness read will appear here automatically. The source repository is where that profile is built.

← All providers · Data indexed from github.com/api-evangelist/lighthouse · machine-readable index on apis.io