> For the complete documentation index, see [llms.txt](https://whitepaper.fruitsblockchain.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.fruitsblockchain.com/1.-basic-development-of-fsfp-fruits-social-finance-platform/1-2.-the-fruits-service-configuration-diagram.md).

# 1-2. The FRUITS Service Configuration Diagram

<figure><img src="/files/9i6RXFfyKW2NcT8izWb4" alt=""><figcaption><p>Figure 3: Diagrams of Fruits Wallet, Fruits Station, etc</p></figcaption></figure>

The main services of FRUITS are as follows: First, each user must download and create an account on the FRUITS Wallet App and/or Web Wallet. From the Wallet, access the FRUITS SDGs Station to donate FRTS and Smile Coins. Once donating Smile Coins, you will be rewarded with various TFSTs (Thanks Fruits Seed Tokens: hereinafter, referred to as "Seed Tokens"), and each Seed Token has a different purpose and value.


---

# 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://whitepaper.fruitsblockchain.com/1.-basic-development-of-fsfp-fruits-social-finance-platform/1-2.-the-fruits-service-configuration-diagram.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.