> 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/pump-mechanism.md).

# PUMP Mechanism

PUMP is the groundbreaking innovation offered by FansHood. Unlike traditional models, FansHood PUMP mechanism allows creators and their supporters to adjust the "A" variable by directly injecting funds, providing a variable growth curve that makes each creator unique to meet different positioning and influence value expressions.

**PUMP maintains consistency with the decentralized spirit by letting direct sponsors and supporters change the "S" and "A" variables**. Every Hood's pricing is strongly related to the content output.

As FansHood grows and the community expands, the current formula and Pump scheme will become more enticing. Centralized governance authority will be transferred to our community, enabling changes in pricing curves and Pump that may better suit the future. Let's explore all possibilities together.


---

# 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/pump-mechanism.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.
