API Layer for Carbon Distribution

Diving deeper into

Brennan Spellacy, CEO of Patch, on the API layer of the carbon stack

Interview
a lot of the projects that ended up not working out were purely focused on technology and not focused enough on distribution and applications of the technology
Analyzed 5 sources

The main lesson is that climate startups win when they turn hard science into an easy buying motion. Patch is built less like a lab and more like a payments network for carbon, where the product is distribution, contracting, and integration into software buyers already use. That matters because early climate technologies often failed when the green option stayed too expensive and too hard to adopt at commercial scale.

  • Patch’s core job is to aggregate project supply, standardize contracts, and let a company or software partner buy carbon through one API instead of negotiating with 10 to 15 separate projects. That is distribution infrastructure, not just climate R&D.
  • The same pattern shows up across the carbon stack. Persefoni focuses on measuring a company’s emissions, while Patch handles procurement of offsets and removals. Each plugs into a specific workflow, which is a more practical go to market model than trying to do everything in one product.
  • The cost gap is still real for frontier removal methods. DOE has described direct air capture as energy intensive and set a target of getting durable carbon removal below $100 per net ton, which shows why commercialization and distribution still matter as much as technical progress.

This market is heading toward climate infrastructure that looks more like fintech than cleantech hardware. The companies that matter most will be the ones that make carbon products easy to discover, compare, buy, and embed into existing software, so new supply can actually reach demand fast enough to scale.