Electra.aero
Electra is an American aerospace manufacturer developing hybrid-electric "Ultra Short" aircraft that combine blown lift with hybrid-electric propulsion to take off and land in roughly 150 feet, removing the runway from regional air travel. Founded in 2020 by Dr. John Langford, the founder of Aurora Flight Sciences, with MIT professors John Hansman and Mark Drela as technical advisors, Electra flew its EL2 Goldfinch technology demonstrator in November 2023 and submitted an FAA Part 23 type-certification application for the nine-passenger EL9 Ultra Short in December 2025. The company reports more than 2,200 pre-orders from over 60 operators, and works both a commercial regional air-mobility market and a defense last-tactical-leg airlift market backed by U.S. Air Force SBIR Phase III and STTR contracts. It is headquartered in Manassas, Virginia, with operations in Cambridge, Massachusetts and Switzerland and a production facility under development at AirPark Ohio adjacent to Springfield-Beckley Municipal Airport. Strategic investors include Lockheed Martin Ventures, Honeywell and Safran. Electra publishes no developer program, API reference or machine-readable specification; the one public, anonymous JSON API it serves is the Statamic CMS content surface behind its newsroom, discovered and documented here by probe.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Electra.aero the way a machine reads it — 7 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 — Electra.aero scores 29.0/100 (thin), with a separate agent-readiness read of 55/100 (agent ready). 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-08-17 · rubric v0.11.0
Put this on your own site. The badge is drawn live from Electra.aero's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/electra.aero/"
title="Electra.aero on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/electra.aero.svg"
alt="Electra.aero Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/electra.aero/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/electra.aero/"
title="Electra.aero on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/electra.aero/card.svg"
alt="Electra.aero Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Electra.aero
Each block below is one kind of artifact we hold for Electra.aero. 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.
Electra.aero Content API
Public, unauthenticated, CORS-open JSON API serving the Electra.aero newsroom — press releases, program milestones and syndicated coverage. This is the default Statamic Content ...
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Electra.aero Content API (news)
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Electra.Aero Rate Limits
RATE LIMITSSecurity 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.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Electra.aero — 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
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 2
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 5
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/electra.aero · machine-readable index on apis.io
This is an independent, third-party profile of Electra.aero, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.