> For the complete documentation index, see [llms.txt](https://tradeleaf.gitbook.io/trade-leaf/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tradeleaf.gitbook.io/trade-leaf/token-economy/token-utility.md).

# Token Utility

The TLF token's utility consists of a reward system and several use cases. The reward system is responsible for allocating tokens as interest or incentive for certain actions performed on the platform in general. The use cases refer to activities that require spending or locking TLF and reTLF tokens.

<mark style="color:purple;">**Platform activities reward:**</mark> The more actions customer performs across all marketplaces, modules, and solutions on the Tradeleaf Platform, the more TLF tokens will be granted to the customer.

It applies to financial operations, such as funding and insurance, and non-financial operations, like deal establishment, order submission, and remote-expert hiring.

<figure><img src="/files/UzFuLzd0qNCPszLYpjjq" alt=""><figcaption></figcaption></figure>


---

# 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://tradeleaf.gitbook.io/trade-leaf/token-economy/token-utility.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.
