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
Lilium website screenshot

Lilium

Lilium was a German eVTOL aircraft developer building the Lilium Jet, a seven-seat (including pilot) ducted-fan electric jet designed for regional air mobility with target cruise speeds around 175 mph and ranges in excess of 100 nautical miles. Lilium pursued concurrent EASA and FAA Type Certification and signed pre-orders with operators across Europe, the Middle East, the United States, Brazil, and Saudi Arabia. In October 2024 Lilium's board approved self-administration for its German subsidiaries after failing to secure a guarantee for a EUR 50 million Bavarian government loan, and in December 2024 the company ceased operations and laid off approximately 1,000 employees. A consortium called Mobile Uplift Corporation GmbH announced a partial asset acquisition in late December 2024, but in February 2025 Lilium's German entities filed a second insolvency after the promised takeover financing failed to materialize. As of this profile (May 2026) Lilium remains non-operational and the website and social channels may be intermittently available; this profile is preserved for historical and archival reference.

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

API Evangelist profiles Lilium the way a machine reads it — 1 machine-readable artifact, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.

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 — Lilium scores 12.7/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 — 12.7/100 · minimal
Contract Quality 0.0 / 25
Developer Ergonomics 1.7 / 20
Commercial Clarity 4.2 / 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

How we profile Lilium

Each block below is one kind of artifact we hold for Lilium. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

Security Posture 1

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

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

Resources

Every other property we hold for Lilium — 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.

Documentation 1

Reference material describing how the API behaves

Access & Security 1

Authentication, authorization, and security posture

Learn 1

Tutorials, courses, talks, and written guidance

Operate 1

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Other 5

Properties that don't map to a standard resource type

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