> For the complete documentation index, see [llms.txt](https://docs.folks.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.folks.finance/folks-token/utilities.md).

# Utilities

{% hint style="warning" %}
Warning: some of the following utilities might still not be live
{% endhint %}

* **Folks Finance Governance** — enables certain active users to steer elements of future protocol development.
* **Folks Router Discounted Fees** — applied to swap transactions through Folks Router on Algorand.
* **Crosschain DEX Aggregator Discounted Fees** — applied to swap transactions through Li.Fi’s crosschain DEX aggregator on xChain.
* **Folks xPortal Discounted Fees** — applied to bridging fees on xPortal (powered by Wormhole NTT).
* **FOLKS as “Gas Token”** — reduce operation transaction fees on xChain by paying in $FOLKS.
* **xGov Voting** — participate in xGov proposal votes on Algorand.
* **Liquidity Incentives** — boost rewards for active market participation.
* **Mobile App and Debit Card Perks** — discounted fees and tiered perks related to Folks Mobile. 
* **Future Utilities** — additional use cases and expanded token utility will be introduced progressively, especially with the launch of Folks xChain V2.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.folks.finance/folks-token/utilities.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.