> 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/regen-registry-overview/objectives.md). # Objectives Regen Registry’s objectives are to: * **Encourage nature-based solutions.** For example, solutions based on regenerative agriculture, conservation, and best management practices, as a strategy to mitigate (by removing/reducing GHG emissions) and/or adapt to climate change. * Provide guidance for, and promote, **scientifically rigorous methodologies and credit classes** to foster the development of high quality ecological assets. * **Create an open-source infrastructure** that allows cost-effective and rigorous MRV implementation, issues and tracks credits while avoiding double counting, and provides payments, billing, and marketing functionality. * **Support best practices** in project-level GHG accounting and ecosystem services. Commercialize innovative types of credits bundled with valuable co-benefits and ecosystem services. * Provide an environment to **develop new types of ecological assets** that will inform voluntary and regulated markets. Incorporate cutting-edge technologies, such as IoT sensors, satellite remote sensing, and digital signatures, in the use of project monitoring and verification. * **Enhance public confidence** in market-based action for GHG removal and ecosystems’ regeneration. --- # 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/regen-registry-overview/objectives.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.