Heliovulcan data catalogue and JSON endpoints

The structured project records published through this catalogue attach an ID, claim type, confidence rating and evidence to each material figure. They are served as free, read-only JSON at stable URLs, so a figure can travel with its assumptions.

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 links
  • GET /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.

Read the labels before the numbers
  • claim_type and confidence are part of the datum — a calculated / low value is a screening output, not a fact about the project;
  • evidence marked unresolved means the source URL is not yet captured — the gap is published rather than papered over;
  • every response includes canonical_url (the human page) and methodology_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.

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.