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

# F2P and Customer Segmentation

●      Free players can be introduced into the game as “flies” or “guardians”. These guardians will not provide any liquidity to the game. However, they can provide action and exist as potential paid customers in the future.

●      Flies would be funded by the paid customers through a mechanic called “mercenaries”.

●      A fly attacking any enemy location on behalf of a faction will gain some “tokens” as a reward. The tokens gained here will be minimal compared to the paid customers.

●      These flies can get “privileged contract” items for fiat currencies and then increase their gains 10-fold.\
\
● Amount of new “free” players will be limited through limited key drops. A user rate of X per hour should be determined after the final calculations


---

# 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://gainhive.gitbook.io/gainhive-whitepaper/gameplay/f2p-and-customer-segmentation.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.