> For the complete documentation index, see [llms.txt](https://docs.openg2p.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openg2p.org/products/open-agri-stack/deployment/farmer-registry.md).

# Farmer Registry

Installing the Farmer Registry.

Step 1 of the [install steps](https://docs.openg2p.org/products/open-agri-stack/deployment.md#install-steps), in the namespace `trial`.

## Install

Follow the Farmer Registry's own guide: [Farmer Registry → Deployment](https://docs.openg2p.org/products/registry/farmer-registry/deployment.md). It installs Commons Base, Commons Services and the Farmer Registry. Set these fields on top:

| Chart            | Field                             | Value                                                                                                                       |
| ---------------- | --------------------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| Commons Services | Exchange Role (Consent Manager)   | **department**                                                                                                              |
| Commons Services | Exchange Domain (Consent Manager) | Empty when the Exchange is at `agrix.<parent domain>`; otherwise its domain                                                 |
| Commons Services | Partner Portal? (Consent Manager) | **No** (the default)                                                                                                        |
| Commons Services | Country Pack                      | The same as every other install (default `ETH`)                                                                             |
| Farmer Registry  | Release name                      | e.g. `fr` (gives the hostname `partner-fr.<domain>`)                                                                        |
| Farmer Registry  | Load Sample Data                  | **On** for a demo only ([sample data](https://docs.openg2p.org/products/open-agri-stack/deployment/testing.md#sample-data)) |

## Check

1. The registry's own checks pass ([Farmer Registry → Deployment](https://docs.openg2p.org/products/registry/farmer-registry/deployment.md)).
2. Note its partner search URL, for the [Composite](https://docs.openg2p.org/products/open-agri-stack/deployment/exchange.md#composite): `https://partner-fr.trial.openg2p.org/dci/registry/sync/search`.
3. Once the Exchange is installed, Partner Management serves the Composite's key:

   ```bash
   curl -s https://partner-management-partner-api.trial.openg2p.org/keys/PARTNER_AGRI_COMPOSITE
   ```

   If not: **Exchange Role** is not `department`, or Partner Management cannot reach `https://agri-composite.<Exchange domain>/.well-known/jwks.json` (set **Exchange Domain**, or **Composite JWKS URL**); the PM staff API log ("Bootstrap").


---

# 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.openg2p.org/products/open-agri-stack/deployment/farmer-registry.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.
