> For the complete documentation index, see [llms.txt](https://funganomics.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://funganomics.gitbook.io/whitepaper/charities/charity-water.md).

# Charity Water

771 MILLION PEOPLE LACK BASIC ACCESS TO CLEAN AND SAFE DRINKING WATER. WE’RE ON A MISSION TO CHANGE THAT. 

Since charity: water was founded in 2006, we’ve been chasing one ambitious goal: ending the global water crisis. And while the water crisis is huge, we’re optimistic. We know how to solve the problem, and we make progress every day thanks to the help of local partners and generous supporters. If we work together, we believe everyone will have access to life’s most basic need within our lifetime. 

<figure><img src="/files/UkoUI1i9WmdUFpUvF8Xu" alt=""><figcaption></figcaption></figure>

Funganomics will support the charity through our token charity funds with a goal of helping millions of people receive sustainable and clean drinking water.


---

# 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://funganomics.gitbook.io/whitepaper/charities/charity-water.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.