Carbonova API.

It is the programmatic interface of CarbonOS, Carbonova’s platform of AI agents. Through REST calls, any system sends activity data, such as fuel or energy use or freight, and gets back Scope 1, 2 and 3 emissions calculated with versioned emission factors. The same API simulates scenarios before an operational change and produces CBAM, CSRD, ISSB and CORSIA reports, with an audit trail.

It is for IT, product and sustainability teams that need carbon calculations inside the systems they already run: ERP, logistics platforms, procurement and supplier portals. It solves three common problems: the same data calculated in different ways by different teams, spreadsheets that cannot keep up with transaction volumes, and emission factors swapped without a record, which makes a number impossible to explain in an audit.

You send activity data in a single call or in batch: litres of diesel, kWh, tonne-kilometres of freight or quantities of purchased material. AI suggests the right emission factor from a database of global factors, the API returns emissions calculated with versioned factors, and webhooks notify your systems of emission events and compliance alerts. Results can feed the CarbonOS inventory with full lineage.

Calculations follow the GHG Protocol Corporate and Scope 3 standards and ISO 14064, and results feed CBAM, CSRD, ISSB (IFRS S1 and S2) and CORSIA reports. Versioning answers a GHG Protocol rule: when a change in methodology or emission factors significantly affects base-year emissions, those emissions must be recalculated. Carbonova does not verify or certify inventories; it hands the verifier the audit trail.

The API runs on the same calculation engine as Carbon Intelligence, the CarbonOS inventory agent. Signal Ingest handles connectors to ERP systems such as SAP and Oracle and to transport systems; Proof Engine keeps the lineage and version of every factor; Supply Chain organises Scope 3 supplier data; and Compliance Hub turns results into reports. The number calculated in your system is the same one in the inventory.

Nothing is lost. Because factors are versioned, each calculation stays linked to the factor version used at the time, and Proof Engine keeps the change history. When a new factor is released, you can recalculate the period in batch and compare it with the previous result, which helps decide whether the change requires a base-year recalculation under your GHG Protocol policy. Published numbers stay explainable.