# Page Not Found

The URL `files/uhKhK9jFIkSN0TTEuS2V` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Why Tonfi Matters: A Glimpse into the Future](https://tonfi-ai.gitbook.io/whitepaper-tonfi.ai/why-tonfi-matters-a-glimpse-into-the-future.md)
- [The Multifaceted Roles of TONFI Tokens in the Tonfi Ecosystem](https://tonfi-ai.gitbook.io/whitepaper-tonfi.ai/the-multifaceted-roles-of-tonfi-tokens-in-the-tonfi-ecosystem.md)
- [Tonfi's Web3 Focus: DeFi and AI Solutions](https://tonfi-ai.gitbook.io/whitepaper-tonfi.ai/tonfis-web3-focus-defi-and-ai-solutions.md)
- [Tokenomics](https://tonfi-ai.gitbook.io/whitepaper-tonfi.ai/tokenomics.md)
- [Vision / Mission](https://tonfi-ai.gitbook.io/whitepaper-tonfi.ai/vision-mission.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://tonfi-ai.gitbook.io/whitepaper-tonfi.ai/why-tonfi-matters-a-glimpse-into-the-future.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://tonfi-ai.gitbook.io/whitepaper-tonfi.ai/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://tonfi-ai.gitbook.io/whitepaper-tonfi.ai/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/whitepaper-tonfi.ai/why-tonfi-matters-a-glimpse-into-the-future.md`).

You may also use `Accept: text/markdown` header for content negotiation.