> 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/g2p-bridge/tech-guides.md).

# Extensions

The G2P Bridge is extensible: the parts that touch external systems are pluggable, so you can adapt it to a specific country, sponsor bank, or delivery model without forking the core.

{% hint style="info" %}
**Start here →** [**How to write your own connector**](/products/g2p-bridge/design-specifications/connectors-and-extensibility.md) — the end-to-end flow: implement an interface, extend the **published Bridge Docker image** (`FROM … + pip install`), select it via config, and deploy. The guides below give the method-by-method contract for each individual interface.
{% endhint %}

Each guide below describes the interface and how to provide your own implementation:

* [Financial address resolver](/products/g2p-bridge/tech-guides/address-resolver.md) — resolve a beneficiary ID to a financial address (e.g. [with SPAR](/products/g2p-bridge/tech-guides/address-resolver/account-mapper-resolution.md)).
* [Sponsor Bank connector](/products/g2p-bridge/tech-guides/bank-connector-interface-guide.md) — integrate a real sponsor bank in place of the Example Bank.
* [Geo resolver](/products/g2p-bridge/tech-guides/geo-resolver.md) — resolve geography for in-kind allocation.
* [Warehouse allocator](/products/g2p-bridge/tech-guides/warehouse-allocator.md) / [Agency allocator](/products/g2p-bridge/tech-guides/agency-alloctor.md) — in-kind fulfilment allocation.
* [Notification connector](/products/g2p-bridge/tech-guides/notification-connector.md) — deliver notifications to partners and beneficiaries.

For the conceptual overview of these extension points, see [Features → Extensibility](/products/g2p-bridge/features/extensibility-connect-to-sponsor-banks.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 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://docs.openg2p.org/products/g2p-bridge/tech-guides.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.