> For the complete documentation index, see [llms.txt](https://guide.geyser.fund/geyser-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.geyser.fund/geyser-docs/product-guides/impact-funds/field-partners.md).

# Field Partners

Field Partners connect Geyser with credible local initiatives.

Geyser brings the tools, contributor community, and capital. Field Partners bring local trust, context, and on-the-ground operations.

Together, they help local realities access Bitcoin capital, financial tooling, and community support.

{% embed url="<https://youtu.be/tXfKm0AbIlw>" %}

***

### Why Field Partners exist

#### To bring Bitcoin funding opportunities to local realities

Bitcoin adoption grows through trusted local people, communities, and projects.

Field Partners help bridge the gap between global contributors and local initiatives by identifying credible projects, supporting their campaigns, and helping them build trust with contributors.

***

### What Field Partners do

#### The ask is simple and dynamic

Field Partners help local projects grow on Geyser by:

* Onboarding local projects
* Hosting workshops
* Promoting campaigns
* Sharing project updates
* Upholding trust and reputation

The more projects Field Partners onboard and support, the more they can be featured and rewarded.

***

### Benefits of becoming a Field Partner

#### What Field Partners receive

**Ongoing earnings**\
Earn sats for onboarded projects and receive

* 10% share of contributions to projects you help bring to Geyser
* 5,000 satoshi per project on-boarded
* incentives to create crowdfunding workshops

**Credibility and reputation**\
Create projects on behalf of beneficiaries, earn a Field Partner badge, appear on the Impact Fund page, and be featured in quarterly reports.

**Access to 0% capital**\
Access recoverable grant capital with 0% interest and obligation-free - a kind of micro-lending - that can be allocated to your circular economy.

***

### Who qualifies?

#### Trusted hubs should already show local traction

We are looking for partners who are already active, trusted, and connected locally.

Strong Field Partners usually have:

* Local community reach
* Workshop experience
* Trust and reputation
* Some funding base
* Prior Geyser usage

***

### Workshops

#### Onboard local projects by hosting workshops

Workshops are a way to become a pillar of your community.

They help Field Partners identify credible local initiatives, teach people how to use Geyser, and turn local activity into fundable projects.

**CTA:** Download workshop resources

***

### Apply

#### Apply to become a Field Partner

Join 100+ partners helping local projects fundraise through Geyser.

Become a Field Partner if you are already active locally and ready to help projects launch, raise funds, host workshops, promote campaigns, and report impact.

Apply here:

{% embed url="<https://airtable.com/appyM7XlNIWVypuP5/shrNXMwb68dmNeMX4>" %}


---

# 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://guide.geyser.fund/geyser-docs/product-guides/impact-funds/field-partners.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.
