> For the complete documentation index, see [llms.txt](https://open-carbon-protocol.gitbook.io/ocp-methodology-requirements/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://open-carbon-protocol.gitbook.io/ocp-methodology-requirements/sections/16.-credit-ownership.md).

# 16. Credit Ownership

To prevent double counting, only one organization can have the ownership of credits initially issued from a project. Projects must provide evidence that they have the right to all carbon credits issued from the project activity, either by (a) proving sole ownership of a project or (b) contractual agreements between the Project Developer and other Project collaborators.

If there are benefit sharing mechanisms, this must be legally agreed upon during the project proposal. Every methodology must establish any steps necessary to ensure that risks of double issuance are addressed (meaning more than one credit is not attached to the same ton of CO<sub>2</sub>e).&#x20;

*<mark style="color:$info;">Default text:</mark>*

<mark style="color:$info;">`“Projects must provide evidence that they have the right to all carbon credits issued from the project activity. Each Project must have one main Project Developer, who will take legal ownership of issued credits. Additional project collaborators should be included in the project proposal, but will not have legal claim to credit ownership to avoid double counting and double issuance.”`</mark>

<br>


---

# 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://open-carbon-protocol.gitbook.io/ocp-methodology-requirements/sections/16.-credit-ownership.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.