> For the complete documentation index, see [llms.txt](https://docs.klimaprotocol.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.klimaprotocol.com/carbon-sellers-handbook/overview-for-carbon-suppliers.md).

# Overview for Carbon Suppliers

Supply eligible carbon credits to the Klima Protocol at programmatically determined execution terms, with automated settlement.

{% hint style="warning" %}
Note: Carbon credits supplied to the protocol are not acquired for resale or trading and may only be accessed through irreversible retirement. Once supplied, credits are permanently removed from circulation and cannot be re-acquired or transferred.
{% endhint %}

### **Overview**

* Transfer a batch of eligible carbon credits to the protocol at quoted, real-time execution terms.
* Receive settlement in USDC (a dollar-denominated stablecoin), or
* Elect to receive kVCM, which may be used to access retirement functionality or participate in protocol coordination signalling.

#### Important Limitations

* Credits supplied to the protocol are **not resold or traded**. They may only be accessed for irreversible retirement.
* All transfers are final. Once secured by the protocol, credits are programmatically locked until retired.
* Only whitelisted credits are currently supported.
* Credits must be in tokenised form.
* Execution terms may update as other participants interact with the system.

Currently supported registries:

* EcoRegistry
* Puro.Earth
* Carbonmark Direct Issuance (CMARK)
* Regen
* UCR

Under evaluation registries:

* Social Carbon
* International Carbon Registry (ICR)
* Rainbow

***

### **Why Supply Carbon to Klima?**

Klima provides structured, rules-based infrastructure for routing eligible carbon credits into retirement markets.

It is designed to reduce friction in execution and settlement compared with traditional bilateral processes, enabling project developers to find a route to market, and tap into carbon credit retirement demand.&#x20;

#### Programmatic Settlement

Carbon supply is executed via smart contracts. Eligible credits are transferred and settled according to predefined rules, without bespoke contracting or manual reconciliation.

#### Continuous Execution Terms

The protocol applies transparent intake conditions and execution parameters based on observable supply and retirement activity. Suppliers can view applicable execution terms at the time of transfer.

#### Demand Connectivity

Retirement demand may originate from direct smart contract interaction or through third-party integrations. Platforms such as Carbonmark provide APIs that enable marketplaces and service providers to facilitate retirement using protocol-supported credits.

#### Traceability

All protocol activity is recorded on a public blockchain. This provides a transparent record from credit intake through final retirement.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.klimaprotocol.com/carbon-sellers-handbook/overview-for-carbon-suppliers.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
