Epirus
Epirus is a Torrance, California-based defense technology company building solid-state, software-defined high-power microwave (HPM) directed-energy systems for counter-electronics and counter-unmanned-aerial-systems (cUAS) missions. Its flagship product is Leonidas, a non-kinetic HPM weapon system designed to defeat single drones and large drone swarms by disabling their onboard electronics, with a growing product family that includes Leonidas IFPC-HPM (Indirect Fire Protection Capability — High-Power Microwave) for the U.S. Army, Leonidas Expeditionary (ExDECS) for the U.S. Marine Corps, Leonidas H2O for maritime interdiction, the portable Leonidas Pod, and Stryker Leonidas (with General Dynamics Land Systems). Epirus also collaborates with Anduril, Northrop Grumman, L3Harris, Kodiak AI, Peraton, and Palantir, and has received contracts from the U.S. Army, U.S. Air Force, U.S. Navy, DARPA, ONR, and Singapore's DSTA. The company is privately held, has raised more than $550M across Series B/C/D, and operates under CMMC Level 2 certification. Its product surface is classified defense hardware and embedded firmware — there is no public developer portal, REST API, SDK, or open-source software offering.
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.
API Evangelist profiles Epirus 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 — Epirus scores 8.1/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
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Epirus
Each block below is one kind of artifact we hold for Epirus. 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 Epirus — 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.
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
Company 9
The organization behind the API
Scroll within the panel for all 9 ·
Other 6
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/epirus · machine-readable index on apis.io