> 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/project-development/monitoring-overview.md). # Monitoring & Verification Regen Registry requires monitoring to be conducted by a project developer or an independent monitor chosen by the project proponent and recognized by Regen Registry. The monitor shall follow the requirements in the approved methodology to collect data and report on the benefits and indicators outlined in the methodology. Monitoring results will be used to determine the crediting amount using calculations defined in the methodology. Each methodology will explicitly specify methods that need to be implemented by a monitor, as well as monitoring event timing, event frequency, and reporting requirements. For most methodologies, the collection of baseline data at the start of a project will be a requirement, so it is important that independent monitors are identified early in the project formation process. At the discretion and expense of Regen Registry, an independent auditor will occasionally verify monitoring reports to ensure appropriate monitoring methods and reporting are being followed. --- # 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/project-development/monitoring-overview.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.