Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Moxion Power website screenshot

Moxion Power

Moxion Power was a Richmond, California-based mobile battery energy storage (BESS) company founded in 2020 that designed, manufactured, and deployed large-scale mobile lithium-iron-phosphate battery units (the MP-75 and related platforms) intended to displace diesel generators across construction sites, film and television production, live events, utility work, and emergency response. The company built a 40,000 square-foot factory in Richmond, raised approximately $100 million in a Series B at a reported $1.5 billion valuation led by Tamarack Global with participation from Amazon's Climate Pledge Fund and Microsoft's Climate Innovation Fund, and signed a multi-year fleet partnership with Sunbelt Rentals. After delivering 400+ units it announced cessation of operations on July 29, 2024, laid off its entire workforce, and filed for Chapter 7 bankruptcy in the District of Delaware in August 2024 with approximately $201,980 in cash on hand and estimated liabilities of $100M–$500M. In September–October 2024, Viridi Parente acquired Moxion's Richmond facility, battery inventory, intellectual property, patents, and the Sunbelt Rentals relationship through the bankruptcy auction for approximately $7 million. Moxion Power had no public developer API, SDK, or open source release; its GitHub organization (github.com/moxion-power) contains zero public repositories. This profile is preserved for historical reference.

human only

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.

Kin Score

API Evangelist profiles Moxion Power 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 — Moxion Power scores 7.9/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 Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 7.9/100 · minimal
Contract Quality 0.0 / 25
Developer Ergonomics 0.4 / 20
Commercial Clarity 0.0 / 20
Operational Transparency 0.7 / 13
Governance 0.0 / 12
Discoverability 6.8 / 10
Agent readiness — 0/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile Moxion Power

Each block below is one kind of artifact we hold for Moxion Power. 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 Moxion Power — 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.

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 1

Authentication, authorization, and security posture

← All providers · Data indexed from github.com/api-evangelist/moxion-power · machine-readable index on apis.io