EnerVenue
EnerVenue is a Fremont, California-based energy infrastructure company building long-duration stationary energy storage using a metal-hydrogen (nickel-hydrogen) battery chemistry derived from NASA-heritage technology that has powered the Hubble Space Telescope and the International Space Station since the 1980s. Co-founded by Stanford materials scientist Professor Yi Cui, EnerVenue refined the orbital nickel-hydrogen cell into a grid-scale "Energy Storage Vessel" (ESV) targeting a 30-year, 30,000+ cycle service life with 100% usable depth of discharge, ~90% round-trip efficiency, an operating range of -20 C to +60 C, no thermal runaway risk, and no active thermal management. The ESV's aqueous metal cell (AMC) uses a nickel hydroxide cathode, a nickel-alloy anode, an alkaline electrolyte, and hermetically sealed hydrogen gas storage built from steel, nickel, fiberglass, resin, and water — no lithium, cobalt, or rare earths. EnerVenue is scaling manufacturing through a one-million- square-foot gigafactory in Shelby County, Kentucky (1 GWh phase one, scaling toward 20 GWh per year with ~$1B of follow-on investment) plus a high-volume line in Changzhou, China (250 MWh by Q3 2026, 1 GWh in 2027). Customer commitments exceed 7 GWh and include Pine Gate Renewables (2.4 GWh, multi-year), Green Energy Renewable Solutions (Nicon Industries), Sonnell Power Solutions, and VedantaESS. The company closed a $300M Series B in 2026 to fund the gigafactory build-out. EnerVenue sells hardware, EPC-integrated storage systems, and long-duration service warranties — it does not publish a developer API, SDK, public OpenAPI specification, or open-source repository.
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 EnerVenue 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 — EnerVenue scores 9.4/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 EnerVenue
Each block below is one kind of artifact we hold for EnerVenue. 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 EnerVenue — 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.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Access & Security 1
Authentication, authorization, and security posture
Learn 2
Tutorials, courses, talks, and written guidance
Operate 2
Status, limits, changes, and where to get help
Company 5
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/enervenue · machine-readable index on apis.io