> 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/structure.md). # Structure The Regen Registry can be divided into three main sections: * The [Regen Registry Handbook](https://handbook.regen.network/) outlines the processes by which different stakeholders can engage in the **creation of new methodologies and programs** used to develop projects and issue credits using features provided by the Regen Marketplace App. * The [Regen Ledger](https://docs.regen.network/) is the **underlying blockchain infrastructure** that stores all information related to claims made on ecological state to provide an open and audible trail for assets issued on our platform. * The [Regen Marketplace App](https://app.regen.network/) is a **front-end application** which allows stakeholders to use Regen Ledger to register projects, buy and sell credits on an open marketplace, and engage in network governance. --- # 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/structure.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.