Patch as Neutral Carbon API Rail

This reveals Patch is trying to become the neutral transaction rail for carbon, not the judge of what counts as good carbon. In practice, that means Patch wants to sit between developers, buyers, and software partners, aggregate supply, standardize project data, and let outside verifiers and ratings firms do the scoring. That separation matters because buyers need a marketplace they can trust not to inflate the quality of inventory it also sells.

• Patch’s actual job is closer to a payments processor or exchange operator. It onboards project developers, digitizes inventory, handles contracting, and adds post purchase monitoring, while using registry data and third party systems as the minimum quality layer rather than acting as the auditor itself.
  1 sacra 2 sacra
• The same separation shows up elsewhere in the carbon stack. Persefoni, a carbon accounting platform, explicitly chose to partner for offsets rather than sell them directly, because combining emissions accounting with offset sales creates the same kind of incentive problem that Patch is describing.
  3 sacra
• That structure also makes room for specialist ratings firms like BeZero, and for marketplaces with different models like Nori. The market is splitting into distinct roles, accounting software, marketplaces, registries, and ratings, because trust improves when no single company controls measurement, grading, and sale of the same asset.
  1 sacra 4 sacra 5 sacra

Over time, the winners in carbon infrastructure are likely to look less like brokers with opinions and more like networks with clear role separation. If Patch keeps owning connectivity, contracting, and portfolio construction while third parties own verification and ratings, it can become the default API and dashboard layer that many carbon applications plug into.