An API allows one machine to talk to another for exchange of resources or data, such as:
http://dataservice.accuweather.com/currentconditions/v1/{Detroit} ==> get current weather conditions in Detroit
https://api.luxand.cloud/photolocation/emotions ==> get emotions of person identified in this photo
The key is, APIs allow companies to interact, share resources, transfer data, etc. programmatically, i.e., directly from one machine to another.
Patch, an API developer focusing on carbon offsets, asserts that:
The road to global carbon-neutrality will be through programmatic compensation. That’s why we’ve built a best in class API to automate your sustainability goals with just a few lines of code.
https://www.usepatch.com/
How does it work? According to TechCrunch:
The company has an API that can calculate a company’s emissions footprint based on an integration with their ERP system, and then invests money into offset projects that are designed to remove an equivalent amount of carbon dioxide.
https://techcrunch.com/2021/02/04/andreessen-horowitz-could-make-the-carbon-offset-api-patch-its-latest-climate-bet/
Translation: Determining the carbon footprint of a large organization like Starbucks is a difficult moving target. So Patch uses an API that connects to the backend financial operating engine of companies (ERP), grabs pertinent metrics, makes certain assumptions, computes Scope 1, 2, and 3 emissions, and connects to offset opportunities to net emissions out to zero. It’s a nice idea. How accurate though? And, does it impact incentives to reduce overall energy use and other forms of emissions, rather than just offsetting?
Bottom line? If it works, this would be a useful step forward towards an API that not only enables offsetting but also the identification of emission reduction opportunities, perhaps by employing generative machine capabilities.