HiTHIUM (Xiamen Hithium Energy Storage Technology Co., Ltd.) is a Chinese energy storage company founded in 2019 that designs and manufactures lithium iron phosphate (LFP) cells, modules and complete battery energy storage systems (BESS) for utility-scale, commercial and industrial, and residential applications. The product line runs from large-format prismatic ESS cells through liquid-cooled multi-megawatt-hour container systems to the HeroEE residential and portable range marketed at hero-ee.com. Company material reports roughly 8,000 staff, more than 1,100 R&D engineers and over 3,900 patents. Product pages publish named certifications including UL 1973, UL 9540, UL 9540A, NFPA 855, IEC 62619, IEC 62477, IEC 63056, IEC 61000 and UN 38.3. HiTHIUM operates a Product Security Incident Response Team (PSIRT) running an IEC 62443-aligned vulnerability management process, and publishes numbered cybersecurity bulletins with CVE references and remediation guidance at hithium.com/support/security.html. HiTHIUM publishes no developer portal, no API reference, no OpenAPI, AsyncAPI, GraphQL or Postman contract, no SDKs, no CLI, no webhook catalog and no MCP or A2A agent surface; third-party integration happens over Modbus/CAN interfaces described in datasheets and manuals that sit behind the download-center account gate, and the HeroEE consumer app's backend is undocumented.
Hithium is profiled on the APIs.io network. Tagged areas include Company, Energy Storage, Battery, Lithium Iron Phosphate, and Renewable Energy.
Hithium’s developer surface includes support, engineering blog, and 11 more developer resources.
Regulatory Posture applies to this provider. Its tags matched the
Energy & Utilities regime, so
Regulatory Posture carries 15 points of the composite.
If this regime is wrong for your business, say so on your
provider repo — the
applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for
this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero:
never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and
several others — scorable at all.
The six quality facets above are damped to 85 points between them,
because the conditional facet above carries the other
15. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 85% of its nominal
weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site.
It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/hithium/"><img src="https://apis.io/badge/hithium/card.svg" alt="Hithium on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
Machine-Readable Auth+10 pts — a served openid-configuration/oauth-authorization-server carrying `issuer` (served), else the securitySchemes class in the provider OpenAPIs — bound (mutualTLS, DPoP, Signature) > negotiable (oauth2 authorizationCode/clientCredentials, openIdConnect) > bearer (http bearer, apiKey) Ask about this →
Idempotency+9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented) Ask about this →
Stable Error Semantics+8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes Ask about this →
13 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.
Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →
aid: hithium
name: Hithium
description: HiTHIUM (Xiamen Hithium Energy Storage Technology Co., Ltd.) is a Chinese energy storage company founded in 2019
that designs and manufactures lithium iron phosphate (LFP) cells, modules and complete battery energy storage systems (BESS)
for utility-scale, commercial and industrial, and residential applications. The product line runs from large-format prismatic
ESS cells through liquid-cooled multi-megawatt-hour container systems to the HeroEE residential and portable range marketed
at hero-ee.com. Company material reports roughly 8,000 staff, more than 1,100 R&D engineers and over 3,900 patents. Product
pages publish named certifications including UL 1973, UL 9540, UL 9540A, NFPA 855, IEC 62619, IEC 62477, IEC 63056, IEC
61000 and UN 38.3. HiTHIUM operates a Product Security Incident Response Team (PSIRT) running an IEC 62443-aligned vulnerability
management process, and publishes numbered cybersecurity bulletins with CVE references and remediation guidance at hithium.com/support/security.html.
HiTHIUM publishes no developer portal, no API reference, no OpenAPI, AsyncAPI, GraphQL or Postman contract, no SDKs, no
CLI, no webhook catalog and no MCP or A2A agent surface; third-party integration happens over Modbus/CAN interfaces described
in datasheets and manuals that sit behind the download-center account gate, and the HeroEE consumer app's backend is undocumented.
deliveryModel:
model: saas
open_source: false
commercial: true
callable_host: false
label: Hosted service · you call their endpoint
confidence: medium
source:
- pricing
generated: '2026-08-28'
method: derived
accessModel:
pricing: unknown
onboarding: unknown
trial: false
try_now: false
public: false
label: Unknown
confidence: low
probe_state: none
source:
- security
generated: '2026-11-13'
method: derived
image: https://www.hithium.com/favicon.ico
url: https://raw.githubusercontent.com/api-evangelist/hithium/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
x-tier: no-public-api
x-tier-reason: Enriched 2026-08-22 with full STEP 0b contract discovery. www.hithium.com and en.hithium.com 404 on /openapi.json,
/swagger.json, /llms.txt and every /.well-known/* path; api., developer., dev., docs., cloud., open., openapi., iot., ems.,
portal. and app..hithium.com do not resolve; hero-ee.com is a Next.js locale catch-all that answers 200 with the same 504KB
HTML shell for /openapi.json and /llms.txt (soft-200, not a document); there is no GitHub organization and the github.com/hithium
user account holds zero repositories. The only machine-adjacent surface found is the site's own internal CMS AJAX (www.hithium.com/ajax/seculist),
which is not a published API.
specificationVersion: '0.23'
created: '2026-08-22'
modified: '2026-08-22'
tags:
- Company
- Energy Storage
- Battery
- Lithium Iron Phosphate
- Renewable Energy
- Utilities
- Manufacturing
- Hardware
- Industrial Control Systems
apis: []
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
- FN: APIs.json
email: info@apis.io
common:
- type: DomainSecurity
url: security/hithium-domain-security.yml
- type: Website
url: https://www.hithium.com/
- type: Support
url: https://www.hithium.com/support/services.html
- type: PrivacyPolicy
url: https://www.hithium.com/privacy.html
- type: Blog
url: https://www.hithium.com/about/IndustryNews.html
- type: Security
url: https://www.hithium.com/support/security.html
- type: Compliance
url: https://www.hithium.com/about/anti_corruption.html
- type: VulnerabilityDisclosure
url: security/hithium-vulnerability-disclosure.yml
- type: Conformance
url: conformance/hithium-conformance.yml
- type: LLMsTxt
url: llms/hithium-llms.txt
- type: Plans
url: plans/hithium-plans-pricing.yml
- type: SecondaryMarketListing
url: https://www.hiive.com/securities/hithium-stock
- type: DataProcessing
url: privacy/hithium-privacy-policy.yml
x-enrichment:
date: '2026-08-22'
status: minimal
artifacts_added: 6
pass: local-v1
x-coverage:
state: none
reason: no-developer-program
detail: 'HiTHIUM sells battery cells and containerised storage systems, not software: there is no developer surface anywhere
on its estate - eleven candidate API/docs subdomains of hithium.com fail to resolve, every /.well-known/* path 404s on
all three live hosts, the HeroEE brand site answers 200 with the same Next.js HTML shell for /openapi.json and /llms.txt
(a soft-200, not a document), there is no GitHub organisation, and the only integration documentation that exists - the
Modbus/CAN datasheets and manuals - sits behind the download centre''s "Please login to download this datasheet" account
gate.'
evidence:
- url: https://www.hithium.com/openapi.json
status: 404
- url: https://www.hithium.com/llms.txt
status: 404
- url: https://www.hithium.com/.well-known/agent-card.json
status: 404
- url: https://www.hithium.com/.well-known/api-catalog
status: 404
- url: https://en.hithium.com/.well-known/security.txt
status: 404
- url: https://www.hero-ee.com/openapi.json
status: 200
- url: https://www.hero-ee.com/.well-known/agent-card.json
status: 404
- url: https://www.hithium.com/support/download_center.html
status: 200
- url: https://www.hithium.com/support/security.html
status: 200
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.