> For the complete documentation index, see [llms.txt](https://prismnetwork.gitbook.io/prismnetwork-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prismnetwork.gitbook.io/prismnetwork-docs/6.-tokenomics/6.3-token-use-cases.md).

# 6.3 Token Use Cases

| Scenario                                 | Description                                                                         |
| ---------------------------------------- | ----------------------------------------------------------------------------------- |
| AI Strategy Account Subscription Payment | Users pay Flux subscription fees with PRSM                                          |
| VIP Tier Benefits                        | Holding PRSM grants higher strategy limits, lower fees, and priority execution      |
| Trading Fee Discounts                    | Use PRSM to offset a portion of trading or routing fees                             |
| Withdrawal Discounts & Burns             | Use PRSM to offset withdrawal fees; a portion of fees is used for buyback and burn  |
| Ecosystem Incentives                     | Incentivizing data contributors, signal collaborators, and strategy developers      |
| B-Side Data & API Services               | Used as payment asset for probability data, market signals, and strategy interfaces |


---

# 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://prismnetwork.gitbook.io/prismnetwork-docs/6.-tokenomics/6.3-token-use-cases.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.