What problem this solves
Screening numbers get quoted. “about 30 GWh per year demand”, “+A$4.6M owner
outcome” — once a figure leaves its report, nobody can tell whether it was a
public EIS statement, a model output or an analyst guess. Heliovulcan publishes the
registry itself: each claim carries its type (public_source,
calculated, assumption…), its confidence, its
limitations and its sources, and every JSON response links back to the human-readable
page and methodology.
Available now
- Versioned static JSON under
/api/v1/, stable URLs - Project, claims and evidence schemas (openapi.json)
- No authentication required
One project is covered, the Remote Mining Asset hybrid-energy Pre-DD screen:
GET /api/v1/projects/remote-mining-asset.json— project entity: identity, location, technology, stats and linksGET /api/v1/projects/remote-mining-asset/claims.json— the claim registry (14 claims)GET /api/v1/projects/remote-mining-asset/evidence.json— the evidence registry (6 objects, access dates and quality ratings)
These are static JSON files served over HTTPS — no authentication, no rate limits beyond the host's, stable URLs. Full field documentation: API docs · machine-readable description: openapi.json · discovery: /.well-known/api-catalog.
claim_typeandconfidenceare part of the datum — acalculated / lowvalue is a screening output, not a fact about the project;- evidence marked
unresolvedmeans the source URL is not yet captured — the gap is published rather than papered over; - every response includes
canonical_url(the human page) andmethodology_url— cite those alongside any figure.
Interactive tools
- Safeguard Atlas — the post-2030 decline rate rebuilt facility by facility, with every assumption adjustable.
- CBAM charge explorer — what the EU carbon border tariff charges each origin country at default values, at a certificate price you set. 198 origins, recalculated in the browser.
Downloadable datasets
Flat files, no authentication, stable URLs. Each is published with the analysis it belongs to, and each carries the licences of the sources behind it — cite those, not this page.
- safeguard-atlas.json and safeguard-facilities.csv — the inputs behind the Safeguard Atlas, 209 register rows. The map layer is not included.
- critical-minerals.json — the record behind critical minerals: power and grid readiness.
- cbam-exposure-by-origin.csv — EU CBAM: the modelled charge at default values for 198 origin countries, split by sector, on 2025 trade and 2026 rules. Updated 2026-10-10.
- cbam-verification-by-origin.csv — the eleven origins with a published country-level steel intensity: the charge at default values against the charge at that country average.
- cbam-sources.csv — every source behind the CBAM figures, with publisher, licence, and whether its values are reproduced or only cited.
The CBAM plant layer is not published: its cross-source identifiers, the matching rules behind them and the per-plant calibrated intensities stay unpublished. What is and is not published, and why, is set out in the CBAM methodology note; the findings are in the verification gap.
Not currently provided
- Search or filtering
- Query parameters or dynamic responses
- Write access
- Service-level availability commitments
Human-readable entry points
The registry structure (project → claims → evidence) extends to further projects and datasets; the URLs will not change if a served endpoint is added later.