LIFT Aircraft
LIFT Aircraft is an Austin, Texas experiential aviation company founded by former Boeing engineer Matt Chasen, built around HEXA — an amphibious electric vertical take-off and landing aircraft with eighteen independent electric motors and propellers, a 432lb carbon fibre airframe, a triply redundant autopilot flown with a single three-axis joystick, an autonomous ballistic parachute, and enough redundancy to fly and land safely with up to six motors disabled. Because HEXA is compliant with the FAA's powered ultralight classification, no pilot's licence is required, and LIFT sells flight as a paid experience rather than selling aircraft — a short training session followed by a solo flight from waterfront bases in Austin and other US cities. The company has raised over $25 million from venture capital, accredited investors and US government grants, has worked with the US Air Force Agility Prime programme and the US Army, and has begun the FAA type certification process for a commercial edition. LIFT publishes no developer REST API or OpenAPI; its only machine-readable surface is a live, unauthenticated Model Context Protocol endpoint and an llms.txt served by its Wix-hosted site.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles LIFT Aircraft the way a machine reads it — 4 machine-readable artifacts across 1 API, 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 — LIFT Aircraft scores 17.9/100 (emerging), with a separate agent-readiness read of 26/100 (agent aware). 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
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile LIFT Aircraft
Each block below is one kind of artifact we hold for LIFT Aircraft. 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.
APIs 1
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
LIFT Aircraft Site MCP
The public Model Context Protocol endpoint served by LIFT Aircraft's Wix-hosted site. Exposes nine tools that let an agent read business details, search the site, read the insta...
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
lift-mcp.yml
MCP SERVERSecurity Posture 2
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 LIFT Aircraft — 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.
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/lift · machine-readable index on apis.io