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
Kairos Power website screenshot

Kairos Power

Kairos Power is an Alameda, California-based advanced nuclear fission company developing the KP-FHR (Kairos Power Fluoride salt-cooled High-temperature Reactor), a Generation IV reactor design that uses TRISO (tri-structural isotropic) fuel pebbles cooled by molten fluoride salt (FLiBe) at low pressure and high temperature. Kairos Power is building Hermes, a low-power demonstration reactor at the East Tennessee Technology Park in Oak Ridge, Tennessee, which became the first non-light-water reactor authorized for construction by the U.S. Nuclear Regulatory Commission in over 50 years (construction permit issued December 2023). A second unit, Hermes 2, will pair two reactors with a 28 MWe electricity-generating turbine. In October 2024 Google signed a corporate power purchase agreement with Kairos Power for up to 500 MW of nuclear electricity from multiple small modular reactors, with the first deployment targeted by 2030 and additional capacity through 2035 — the first corporate PPA for new advanced nuclear in the United States. The company's revenue model is reactor sales, electricity PPAs, and federal cost-share partnerships (DOE Advanced Reactor Demonstration Program). Kairos Power is privately held, does not expose a public developer API or SDK, and operates under NRC regulatory oversight as a safety-critical nuclear licensee.

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 Kairos 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 — Kairos Power scores 7.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 Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 7.4/100 · minimal
Contract Quality 0.0 / 25
Developer Ergonomics 0.0 / 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 Kairos Power

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

Kairos Power Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Every other property we hold for Kairos 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

Learn 1

Tutorials, courses, talks, and written guidance

Operate 1

Status, limits, changes, and where to get help

Other 4

Properties that don't map to a standard resource type

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