> For the complete documentation index, see [llms.txt](https://docs.fanshood.io/mainpage/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fanshood.io/mainpage/fanshood-economic-model/fans.md).

# Fans

Creators are a vital part of FansHood, and we pay special attention to the influence expansion of content creators. FansHood provides Fans as a support program for content creators based on their content output. 

Fans can be acquired in various scenarios such as videos, dynamic modules and trading Hoods. 

After obtaining Fans Tools, content creators can promote their content through FansHood's content recommendation platform, gaining greater exposure and expanding their influence. 

As the FansHood ecosystem gradually expands in the future, we will also conduct airdrops and provide other benefits of Fans. 

**In the progression of the ecosystem, FansHood will continuously adjust Fans acquisition data in real time at the end of each cycle to support the positive development of the entire ecology.**


---

# 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.fanshood.io/mainpage/fanshood-economic-model/fans.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.