Zap Energy
Zap Energy is a Seattle, Washington fusion energy company pursuing commercial fusion power via the sheared-flow-stabilized Z-pinch — a compact, magnet-free pulsed-power approach in which a flowing column of deuterium plasma is compressed (pinched) to fusion conditions inside a roughly two-meter metal tube, with shear in the axial flow stabilizing the pinch in place of the heavy superconducting magnets used by tokamak and stellarator designs. Founded in 2017 by Benj Conway, Brian A. Nelson, and Uri Shumlak as a spinout of University of Washington and Lawrence Livermore National Laboratory research, the company has developed a lineage of devices — ZaP, ZaP-HD, FuZE, FuZE-Q, and FuZE-3 — culminating in 2024 with Century, a 100-kW-scale repetitive pulsed-power test platform with liquid-metal walls intended to demonstrate plant-relevant technologies. In November 2025 FuZE-3 reported plasma electron pressures of 830 MPa (1.6 GPa total), the highest pressure measured in any sheared-flow-stabilized Z-pinch and a marker on the path to scientific energy gain (Q>1). Zap Energy was selected for the U.S. Department of Energy's Milestone-Based Fusion Development Program in May 2023 and received DOE approval of the preconceptual design of its Fusion Pilot Plant. The company has raised over $325 million across Series A–D from Breakthrough Energy Ventures, Lowercarbon Capital, Energy Impact Partners, Chevron Technology Ventures, Shell Ventures, DCVC, Valor Equity Partners, and Addition. As of April 2026, Zabrina Johal serves as CEO with Conway as President, and the company has expanded its mandate to also pursue small modular fission alongside its fusion roadmap. Zap Energy has no public developer API, SDK, GitHub organization, or open-source release; the technical surface is published as peer-reviewed papers and DOE milestone reports.
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 Zap Energy 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 — Zap Energy 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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Zap Energy
Each block below is one kind of artifact we hold for Zap Energy. 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 Zap Energy — 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 6
The organization behind the API
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/zap-energy · machine-readable index on apis.io