> For the complete documentation index, see [llms.txt](https://help.eq-earth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.eq-earth.com/registry/contact-us.md).

# Contact Us

For any question about the Equitable Earth Registry, your account or a transaction, email the Registry team at [**registry@eq-earth.com**](mailto:registry@eq-earth.com).

## Help us answer quickly

In your email, include:

* your organization's name, as registered in the Registry;
* the email address you use to sign in;
* what you were trying to do, and what happened instead;
* for a transfer or retirement: the serial number(s), the quantity, the date and the other account holder or beneficial owner involved;
* a screenshot of any error message.

{% hint style="danger" %}
Never send your password or a verification code by email. The Registry team will never ask for them.
{% endhint %}

## Other questions

For questions about the Equitable Earth Standard, the Programme or project certification, contact <info@eq-earth.com>.


---

# 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://help.eq-earth.com/registry/contact-us.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.