How to integrate with the Intervention module

Used to measure the impact of regenerative practice changes for verification by carbon standards.

Overview

Regrow’s Intervention module quantifies the impact of regenerative agricultural practice changes by calculating greenhouse gas emissions and removals. It is powered by DNDC, Regrow’s scientifically-rigorous soil model. DNDC measures nutrient cycling and changes in soil carbon to model GHG outcomes resulting from adoption of agricultural practice changes. The GHG quantification data provided by the API can be used for reporting and verification to carbon standards for carbon asset generation.

The Intervention module processes farm management (e.g., crop, tilling, fertilizer) and field conditions (e.g., weather, soil) to generate greenhouse gas emissions data for quantifying carbon assets. It incorporates historical events and specific regenerative practices, producing results that reflect the quantified credits from these practices. Outcomes are determined based on a designated carbon protocol, yielding scope-specific assets with associated uncertainty.

Integration workflow

Integrating with the API includes four phases: creating projects, uploading field data to a project, submitting projects for quantification and receiving project outcome results.

Create a Project

The first step to get started using Measure API is to create a project. A project is a grouping of agricultural fields. All of the fields that are ultimately added to the project will be modeled together.

Project name

Give your project a unique title that will help you remember and track the project. Here are a few examples:

Protocol

A protocol is a defined methodology for quantifying carbon credits, including baseline logic, uncertainty application rules, and carbon asset calculations. Regrow supports credit quantification with leading Scope 1 protocols such as Verra VM0042 and CAR's Soil Enrichment Protocol. Additionally, Regrow supports general protocol logic for Scope 3 projects.

Select the protocol option for that aligns with the Protocol your project is following or your project verifier. The protocol selected for the project sets the Scope of the project. For Scope 1 choose the vm0042 protocol or the SEP protocol. For Scope 3 projects, choose the General Scope 3 protocol. If you select the General Scope 3 protocol there is an additional parameter to set.

Reporting Percentile

The reporting percentile defines the uncertainty adjustment for the project. This is the percentile of the uncertainty distribution that final credit value will be taken from. In Scope 1 projects, the protocol defines the required reporting percentile to use. For Scope 3 projects, there is more flexibility for project developers to choose and defend the reporting percentile. The default value for the reporting percentile with Scope 3 projects is 33, but you can override that value by setting this parameter.

Baseline Method

The baseline method determines the logic used to generate a counterfactual baseline from a history of field management practices. Depending on the protocol selected for the project, you may need to select the baseline method.

Additionally, you can optionally set parameters to extend the GHG Boundary for the project. By default the GHG boundary for all projects includes Soil Organic Carbon (SOC), Soil Methane (CH4), and Direct and Indirect N2O. You can choose to include additional emissions types to be quantified with the project by setting one of the following parameters:

Optional GHG Boundaries

For Scope 1 projects, optional boundaries include fossil fuel emissions, liming emissions, and enteric CH4. Selecting these may require additional field data, such as fuel consumption for fossil fuel emissions.

For Scope 3 projects, the optional boundary includes fossil fuel emissions, which also necessitates fuel consumption data for each field if selected.

Step 2: Upload Fields to the Project

The next step is to submit fields to the project. A project can have any number of fields, but it’s best practice group fields with some commonality into projects. For example, fields can be grouped into projects based on a region (such as a country or climate region), a crop type (such that all fields growing the same crop are in a single project), or a reporting time period (such as a crop year).

A field (also referred to as a session input) is a collection of field data (such as field boundaries), field conditions (such as soil data) and farm management events (such as crop, tillage, irrigation and nutrient management data).

You’ll need to make a single request for each field in the project.

The DNDC model powering the Measure API is calibrated for specific farm management practices (also referred to as “events”), field metadata and conditions. The table below outlines the relevant agricultural information used to model GHG outcomes. Not all data in the table is required, and some field management events listed below will not be applicable for every field.

Step 3: Finalize the Project

After all the desired fields have been added to the project it can be finalized. Finalizing a project indicates that all field data has been submitted and the project is ready for modeling. Once a project is finalized, DNDC will run.

Step 4: Retrieve Project Outcomes

After the project and field outcomes have been modeled + the QA process is complete, you can retrieve the outcomes from one of the results endpoints. There are two results endpoints, one for Scope 1 projects and one for Scope 3 projects.

Hint: The scope of the project is determined from the selected protocol. VM0042 and SEP protocols result in Scope 1 projects, while General Scope 3 protocol results in a Scope 3 project.