> For the complete documentation index, see [llms.txt](https://trading-labs.gitbook.io/aifinbotx/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://trading-labs.gitbook.io/aifinbotx/aifinbotx-whitepaper-en/tokenomics/7.3.-core-mechanism-design.md).

# 7.3. Core Mechanism Design

#### 1. Utility-driven value

Token value comes from real usage, not pure speculation.

***

#### 2. Multi-scenario utility demand

AIFX is used across multiple ecosystem scenarios:

* AI compute payments
* AI trading access
* Travel spending
* Payment settlement

***

#### 3. Staking rewards

Users can stake to receive:

* Ecosystem revenue sharing
* Network rewards
* Governance rights
* Service priority

***

#### 4. Buyback and deflation mechanisms

Part of ecosystem revenue is used for:

* Market buybacks
* Token burns
* Long-term value support


---

# 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://trading-labs.gitbook.io/aifinbotx/aifinbotx-whitepaper-en/tokenomics/7.3.-core-mechanism-design.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.