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
X-energy website screenshot

X-energy

X-energy is an advanced nuclear reactor and fuel company headquartered in Rockville, Maryland, founded in 2009 by Dr. Kam Ghaffarian. The company's flagship product is the Xe-100, an 80 MWe (320 MWe four-pack) high-temperature gas-cooled small modular reactor (SMR) using helium coolant and TRISO-X pebble fuel, designed to deliver both electricity and high-temperature process steam to industrial customers. X-energy's fuel subsidiary, TRISO-X, is building a commercial TRISO fuel fabrication facility in Oak Ridge, Tennessee. Project pipeline includes a four-unit Xe-100 plant for Dow Chemical at Seadrift, Texas (NRC environmental assessment completed May 2026, the first US advanced reactor environmental review to be completed), a 12-unit Xe-100 deployment with Energy Northwest at the Tri-Cities, Washington site, a collaboration with Amazon Web Services for data-center power, a feasibility study with LG&E and KU in Kentucky, work with Ontario Power Generation in Canada, and selection under the US Department of Energy's Advanced Reactor Demonstration Program (ARDP). X-energy is led by CEO J. Clay Sell and Chairman/founder Dr. Kam Ghaffarian. Investors include Amazon (Climate Pledge Fund), Ares Management, Citadel, Segra Capital Management, Jane Street, Ken Griffin, the University of Michigan, and others. X-energy completed an upsized IPO on Nasdaq in April 2026. The company does not publish a public developer API or SDK.

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 X-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 — X-energy scores 7.2/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.2/100 · minimal
Contract Quality 0.0 / 25
Developer Ergonomics 0.4 / 20
Commercial Clarity 0.0 / 20
Operational Transparency 0.0 / 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 X-energy

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

X Energy Domain Security

TLSv1.3 · DMARC

SECURITY

Resources

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

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