> For the complete documentation index, see [llms.txt](https://handbook.regen.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.regen.network/credit-type.md). # Credit Type - [Key Protocol Components](https://handbook.regen.network/credit-type/key-protocol-components.md) - [Credit Type](https://handbook.regen.network/credit-type/credit-type.md): Each credit protocol is associated with a credit type that defines the primary unit of measurement used to quantify the ecological asset being traded (i.e. carbon, biodiversity, etc). - [Co-Benefits](https://handbook.regen.network/credit-type/co-benefits.md): A credit protocol may define a series of ecological and social co-benefits indicators to apply in conjunction with the approved protocols. - [Writing a Credit Protocol - Guidelines](https://handbook.regen.network/credit-type/writing-a-credit-protocol-guidelines.md): Project eligibility, rules and regulations, GHG removal and emission reduction requirements if applicable - [Credit Class Template](https://handbook.regen.network/credit-type/writing-a-credit-protocol-guidelines/credit-class-template.md): The credit class template may be used to help with credit class writing - this is a guide to be followed or adapted as needed. --- # 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://handbook.regen.network/credit-type.md?ask=&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.