One emissions engine, three interfaces, no API keys
The problem
Carbon accounting tools either put the factors behind a subscription or the methodology behind a dashboard. An agent asked to calculate emissions needs both the numbers and the audit trail, offline.
What we built
967 emission factors from six free, peer-reviewed sources ship with the package. No key, no network call, no vendor between the calculation and the citation.
A CLI for humans, an MCP server for agents, and a Claude Code skill for coding sessions all call one calculation core, so the three interfaces cannot disagree about a number.
Every result names the factor it matched, the basis on which it matched, and the source database, which makes the output reviewable by someone who did not run it.
Interactive HTML reports with maps turn a scope inventory into something a board can read, generated from the same run that produced the JSON.
What this demonstrates
Domain engines packaged for agent consumption, with the citation trail intact.
Get in touch
Tell us what you are trying to build and what is in the way. We will tell you early if we are not the right fit.