For software vendors

High accuracy emission factor matching, inside your product

Your users upload a procurement file to you. You send the lines to one endpoint and get back the factor, the library, the boundary, the emissions and the reasoning for each one. The hard part of Scope 3, without a data team of your own.

POST/v1/matchbatch, 5,000 lines
{"description": "ACIER BETON HA B500B 12MM""quantity": 3000"unit": "kg""country": "FR""line_id": "client-42"}
Response
{"activity": "Reinforcing steel, hot rolled""library": "ADEME 23.6""region": "FR""boundary": "cradle_to_gate""emissions_kgco2e": 6990"confidence": "high""rejected": ["Steel, low alloy", "Steel section, hot rolled"]"reasoning": "B500B is a reinforcing grade, not a structural section."}

One call per batch. The factor, the library, the boundary, the emissions and the reasoning come back on every line.

96%of lines usable as returned, on the open benchmarkread the benchmark
269,551emission factor values behind one endpointmore coming
…libraries, normalised into one schemamore comingsearch the open data
2 htime to first result in your MCP

What it changes for your product and your P&L

A footprint in the first session

Your user uploads the file they already have and sees a number, instead of being asked to fill in a template first.

Quality that makes your product scale

Any prototype can match the easy 10% of a file. Your users only save time if the other 90% comes back right too, which is the number we publish and keep measuring.

Your engineers on your roadmap

No ingestion pipeline, no factor curation, no unit vocabulary to maintain. One endpoint and a schema that does not move.

The data stays yours

Your account, your keys, your region and your data-processing terms, with usage and logs on your side.

Library updates off your plate

Publishers revise, retire and renumber. That lands here and reaches you as the same schema it always was.

20x cheaper than building it

Counted against a data team, an ingestion pipeline and the yearly re-import of every library you support.

Time to first result

Hours over MCP. Days over REST.

  1. Day 02 hoursOver MCP

    A key, the MCP server pointed at your assistant, and a file matched end to end.

  2. Week 12 to 3 daysOver REST

    The REST endpoint wired into your upload flow, with the confidence bucket driving your review screen.

  3. Week 2your callYour own factors

    Your own factors matched beside the open ones, and your identifiers returned alongside ours.

Make or buy

What building it yourself actually costs

What it takesBuild itUse open-climate.ai
Ingesting and normalising every public libraryOpen dataYour teamIncluded
Following every publisher revisionOpen dataYour teamIncluded
One boundary, unit and warming vocabularyOpen dataYour teamIncluded
The matching itself, at a defensible accuracySee what features you needYour teamIncluded
The reasoning trail an auditor will ask forSee what features you needYour teamIncluded

What people say

In a couple of hours, open-climate.ai's MCP was integrated into Carbon+Alt+Delete.
HanspeterCTO, Carbon+Alt+DeleteLeading GHG accounting tool · Belgium

Put it in front of your customers this quarter

Tell us what your users upload and where the result has to land. We will work out the shortest path to it.

Choose a filexlsx or csv, any shape. No template, no cleanup week.
  • EU hosting
  • Never used to train language models
  • Confidentiality guaranteed