Agoro Carbon USA Cropland Program
Score Breakdown
Integrity
verified Additionality confirmed by the VVB (SCS Global Services) per the monitoring/validation materials
missing Reversal treatment not addressed in the extracted record and two corrective actions outstanding, lowering permanence confidence
Transparency
verified VVB named (SCS Global Services) and monitoring/validation documents present with recent dates (monitoring report 2025-05-21, validation report 2025-11-10)
missing Key quantified fields missing or unverified: total verified emission reductions not provided, leakage deduction percent not in the monitoring record
Claim Safety
verified Project is not CORSIA-eligible, reducing double-claim risk from that channel
inferred Leakage justification is reported as quantified in the validation report (2025-11-10) but the PDD did not address leakage — contradiction creates uncertainty
Documentation
verified Multiple documents available (PDD, monitoring report, validation report) and extraction confidence is high
missing Two corrective action requests and multiple contradictions between documents indicate reliability issues in the record
Detailed Analysis
Integrity
Additionality is supported by a barrier test and was confirmed by the VVB (SCS Global Services) in project documentation, which is a positive. The project uses a project-specific baseline (VM0042 methodology v2.0) and there is no record of a recent baseline reassessment, reducing baseline robustness. A 22% buffer pool is in place, which helps permanence, but the extracted facts state reversal events are 'not addressed' and two corrective action requests were issued, undermining permanence confidence. Overall these mixed signals yield a moderate integrity score.
Transparency
The VVB is identified and both a monitoring report (2025-05-21) and a validation report (2025-11-10) are in the record, which supports transparency. However, the monitoring record lacks the verified ERR total and does not state a leakage deduction percent; usage monitoring method and verified usage rates are also absent. Extraction confidence is high, so missing fields reflect genuine documentation gaps rather than extraction error.
Claim Safety
The project is not CORSIA-eligible, lowering double-claim risk via that channel. The validation report indicates leakage was quantified, which is positive for claim safety, but the PDD earlier did not address leakage and several monitoring fields (usage monitoring, verified ERR) are missing. These contradictions and gaps increase the risk of over‑crediting or weak claims.
Documentation
There are multiple evidence documents listed (PDD, monitoring report, validation report) and 20 documents used with high extraction confidence, and the monitoring report is recent (2025-05-21) with a later validation (2025-11-10). Nonetheless, two corrective action requests were issued and several contradictions exist between documents, indicating the documentation package is imperfect and still under resolution.
Overall
I privileged the later or higher-priority document on each contradiction but noted the effect on confidence: for the leakage justification I privileged the validation report (validation report dated 2025-11-10 is later and more authoritative than the PDD dated 2025-04-24), accepting 'quantified' leakage as the working value. For FPIC, grievance mechanism, safeguards, and benefit sharing I privileged the monitoring report (monitoring report dated 2025-05-21 is later than the validation report dated 2024-12-03) and therefore treated those items as present, but these opposing statements across documents indicate inconsistent record keeping. For the crediting period contradiction I privileged the validation report value (validation report dated 2025-11-10 is later than the monitoring report/PDD), adopting the 2021-05-20 — 2042-05-20 period stated in the validation report. Because contradictions are present and corrective actions were issued, I reduced scores to reflect reliability concerns despite several positive elements (VVB verification, buffer pool).
Audit Analysis
The project shows some important strengths (VVB verification of additionality, a 22% buffer pool, and a recent validation report clarifying leakage). However, contradictions across documents, two corrective action requests, and several missing quantified fields (verified ERR, leakage deduction percent, usage monitoring) reduce confidence and increase risk of over‑claiming.
Project Description
Proponent: Agoro Carbon Alliance US Inc. Protocol categories: Agriculture Forestry and Other Land Use Protocols: VM0042 Estimated annual GHG reductions: 306507 tCO2e Region: North America Registration date: 2025-11-21
Red Flags
- Contradictory statements between PDD, monitoring report, and validation report on leakage, FPIC, grievance mechanism, safeguards, benefit sharing, and crediting period
- Reversal treatment listed as 'not addressed' in extracted record and two corrective action requests issued
Credit Vintages
Nessuna emissione registrata sul registro.
Cosa migliorerebbe questo punteggio
- Publish a reconciled document or amendment that resolves contradictions (leakage, FPIC, grievance, safeguards, benefit sharing, crediting period) and references the authoritative dates
- Provide verified totals and missing quantified fields in the monitoring/verification package (verified ERR, leakage deduction percent, usage monitoring method and verified usage rates) and close corrective actions
Questi suggerimenti indicano quali prove pubbliche aggiuntive potrebbero migliorare il livello di confidenza di questa valutazione. Non garantiscono un punteggio futuro più alto.
Risk Indicators
VVB-confirmed
buffered but reversals unclear
quantified but inconsistent docs
project baseline, reassessment unclear
partially documented; contradictory
CORSIA no, CCP status unknown
Where to buy
+ Know where to buy this?
Listing multiple projects? Send us a CSV at [email protected].
⚑ Dispute this rating
Sei il proprietario di questo progetto?
Correzione metadati (gratuita)
Nome, paese, marketplace o link errati? Segnalacelo.
Non modifica lo score.
[email protected] →Rivalutazione con nuovi documenti
Hai documentazione aggiornata non ancora inclusa? Puoi richiedere un nuovo run della pipeline con i nuovi input.
Invia Documenti →