> 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/pbms/developer-zone/tech-guides/registry-connectors.md).

# Registry Connector

This guide provides details on implementing the [Registry Connectors Interface](https://github.com/OpenG2P/pbms/tree/develop/extensions/openg2p-bg-task-registry-adapters) for integration with PBMS Background Tasks.

## Overview

The `RegistryInterface` defines a standardized contract for interacting with various **G2P Registries** within the PBMS. It ensures consistent behavior across different registry integrations, including eligibility checks, summary computation, entitlement processing, and beneficiary search functionalities.

Custom implementations of this interface allow developers to integrate new registry types (for example, `farmer`, `student`, or `worker` registries) without modifying the PBMS core logic.

**Interface Code:** [Registry Interface](mailto:undefined) in OpenG2P PBMS Background Tasks Extensions\
**Example Implementation:** [`farmer` Implementation](https://github.com/OpenG2P/pbms/blob/develop/extensions/openg2p-bg-task-registry-adapters/src/openg2p_bg_task_registry_adapters/computations/registry_farmer.py), [`households` Implementation](https://github.com/OpenG2P/pbms/blob/develop/extensions/openg2p-bg-task-registry-adapters/src/openg2p_bg_task_registry_adapters/computations/register_household.py)

{% content-ref url="/pages/WUxgS9gl47l9MxPTZh5w" %}
[Key Components](/products/pbms/developer-zone/tech-guides/registry-connectors/key-components.md)
{% endcontent-ref %}

{% content-ref url="/pages/NXAuwaTYD2hNdEsaVCwK" %}
[Example Implementation Workflow](/products/pbms/developer-zone/tech-guides/registry-connectors/example-implementation-workflow.md)
{% endcontent-ref %}


---

# 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/pbms/developer-zone/tech-guides/registry-connectors.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.