> For the complete documentation index, see [llms.txt](https://docs.energyweb.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.energyweb.org/launchpad/generic-and-energy-services/green-proofs-as-a-service.md).

# Green Proofs as a Service

<figure><img src="https://989391867-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtVv4gal2xiLAecbIlZ7d%2Fuploads%2FvSpRM1FSwmRAx2I4ouJK%2FGPSaaS.jpg?alt=media&amp;token=9dc439b1-1eea-4914-a396-175730ef8cef" alt=""><figcaption></figcaption></figure>

Green Proofs as a Service allows green start-ups and enterprises alike to create Proof of Concepts for demonstrating emission reduction savings through the creation of ready-to-go registries.

You can configure your registry to accommodate your requirements and you don't have to be a developer to do it.&#x20;

Examples of emission savings products include:

1. Sustainable Aviation Fuel ( marking the difference between regular fuel and low emissions fuel)
2. Maritime Sustainable Fuel ( marking the difference between regular fuel and low emissions fuel)
3. Green Proofs for Bitcoin ( demonstrating the use of renewables vs fossil fuel energy)
4. Your next project can be showcased here.&#x20;

To see how it works you can go here [Quickstart Guide](https://docs.energyweb.org/launchpad/generic-and-energy-services/green-proofs-as-a-service/green-proofs-as-a-service-quickstart-guide.md) or see the [full description](https://docs.energyweb.org/launchpad/generic-and-energy-services/green-proofs-as-a-service/registry-functionalities-and-processes.md) of all functionalities (both configurable and inside the platform) or consult the technical diagram below.&#x20;

<figure><img src="https://content.gitbook.com/content/tVv4gal2xiLAecbIlZ7d/blobs/PCHCz8SFfd3lshxx16NJ/image.png" alt=""><figcaption><p>Technical Diagram of the GPSaaS</p></figcaption></figure>


---

# 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://docs.energyweb.org/launchpad/generic-and-energy-services/green-proofs-as-a-service.md?ask=<question>&goal=<user_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.
