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

# Introduction

WeFund is a multichain incubation and crowdfunding platform that uses blockchain and smart contracts to make the process more transparent, hold project creators accountable, and minimize risk for project backers. WeFund is developed to be a platform for a large community of blockchain project investors and builders. WeFund primarily focuses on blockchain projects that have real-world applications and utility in the industries of healthcare, the environment, finance, education, and more. <br>

In addition to the platform, WeFund provides a customizable crowdfunding smart contract infrastructure API that includes WeFund's milestone system, backer approval, yield generators, and smart contracts for single and multi/cross chain in Solidity and Rust.


---

# 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://wefund.gitbook.io/wefund-whitepaper/wefund/introduction.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.