> For the complete documentation index, see [llms.txt](https://help.maearth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.maearth.com/resources-for-trusted-evaluators/about-trusted-evaluators/how-to-become-a-trusted-evaluator.md).

# How to become a trusted evaluator

**Trusted evaluators are invited directly by Ma Earth.**

While there is no open application process right now, we're always learning about people doing excellent work in this space. 

If you would like to become a trusted evaluator, please [contact us](https://maearth.com/contact). We'll keep you in mind as the network grows.

#### What happens after I'm invited?

**If you do not have an organization profile on Ma Earth:**

1. You'll receive an invitation email from Ma Earth
2. Accept the invitation and create your organization profile
3. Start endorsing organizations you know and trust

**If you already have an organization profile on Ma Earth:**

1. You'll receive an email notifying you that you are now a trusted evaluator
2. Start endorsing organizations you know and trust

#### Can my organization have multiple members?

**Yes.** If your organization is a trusted evaluator, we encourage you to [invite team members to your organization page](/resources-for-land-stewards/organization-profile/organization-members.md).


---

# 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.maearth.com/resources-for-trusted-evaluators/about-trusted-evaluators/how-to-become-a-trusted-evaluator.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.