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

# Mission

With Follows, we are building a '**socialfi**' ecosystem where creators can thrive financially and creatively while fans are rewarded for their support and engagement. The goal is to empower both creators and fans in a mutually beneficial ecosystem.

**Our mission at Follows is to safeguard users against data exploitation while providing equitable earning opportunities for all**. By prioritizing user privacy and ensuring that every individual has a fair chance to earn, we strive to foster a community where creativity thrives and users are empowered to monetize their content without compromise

**Our aim is to establish a creator-first ecosystem, where creators receive 95% of all post-expense revenue.** The practicality and scalability of this model in the real world is yet to be tested, and the only way to assess its effectiveness is through attempting it ourselves.


---

# 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://follows.gitbook.io/follows/mission.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.