> 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/developers-handbook/overview.md).

# Overview for Developers

All Klima Protocol functions are permissionless, meaning they can be automated and integrated into any software system. Examples include:

* Programmatically retiring carbon credits for your customers or your organisation.
* Integrating access to retirement-eligible carbon credits into existing applications or storefronts.
* Fetching real-time execution quotes for carbon supply and retirement.
* Analysing carbon market activity and protocol state via onchain data.
* Building automations or alerts based on protocol pricing signals and activity.

For now, try experimenting with the [Carbonmark API](https://docs.carbonmark.com/) which already supports many of these capabilities today.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.klimaprotocol.com/developers-handbook/overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.