Lytro
Lytro was a light-field (plenoptic) imaging company founded in 2006 by Ren Ng and based in Mountain View, California. It shipped the first consumer light-field cameras (the Lytro and the Lytro Illum), which captured the entire light field so images could be refocused after the fact, and later pivoted to professional light-field capture for cinema and VR with Lytro Cinema and Lytro Immerge. Backed by a16z, Greylock, NEA and Qualcomm Ventures, the company wound down in March 2018 with much of its technology and talent moving to Google. It is defunct and publishes no public developer program or API; the lytro.com domain now 301-redirects to an unrelated light-field vendor (raytrix.de).
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.
Lytro 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 — Lytro 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.
Lytro 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/lytro · machine-readable index on apis.io