> For the complete documentation index, see [llms.txt](https://wp2.enrex.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wp2.enrex.io/4.-enrex-ecosystem/4.2.-enrex-offsetting-solutions/4.2.1.-web-offsetting-widget.md).

# 4.2.1. Web Offsetting Widget

The introduction of a widget of sorts, that traces and offsets carbon emissions expediently generated by website attendance. Not only does Enrex concern themselves with cleaning out the cryptocurrency and blockchain environment, but we have also opted to branch out to simple web offsetting operations as well.

The main goal of the Widget is to provide an additional voluntary solution for certain website visitors and their handlers to offset their visitation emissions. Furthermore, the Widget provides a broader exposition for Enrex and its native token - $ENRX.

The widget epitomises a standard or a sign of approval. It symbolises a certain business's or website's determination to go in the direction of a greener side of the industry - an act of serious positioning within the environmental concern debate. 'Widgeting' a website - announcing one's willingness to go carbon neutral.

Within the widget's properties, one gains viewership access to full energy consumption and widget usage analytics. Among those, there are:

* A full roster of websites already using the Enrex widget.
  * Inside a singular entry: kWh usage average for single and annual visits; CO2 amounts produced by single and annual visits.
* A full accounting of kWh consumption and CO2 generation.
* A full amount of visitors who have used the widget to offset their visitation.

Every yearly quarter Enrex issues an appropriate financial offset instrument to account for that quarter's calculated energy consumption and CO2 emissions (e.g. renewable energy certificates, carbon allowances, etc.).


---

# 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://wp2.enrex.io/4.-enrex-ecosystem/4.2.-enrex-offsetting-solutions/4.2.1.-web-offsetting-widget.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.