# Page Not Found

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

## Suggested Pages

You may be looking for one of the following:
- [什麼是 「 最小手數 」 ？](https://sofinx.gitbook.io/sofinx-help-center-zh/bang-zhu-zhong-xin/faq/shen-mo-shi-zui-xiao-shou-shu.md)
- [什麼是 SoFinX?](https://sofinx.gitbook.io/sofinx-help-center-zh/bang-zhu-zhong-xin/qi-cheng-sofinx/shen-mo-shi-sofinx.md)
- [什麼是 SoFinQ?](https://sofinx.gitbook.io/sofinx-help-center-zh/bang-zhu-zhong-xin/qi-cheng-sofinx/shen-mo-shi-sofinq.md)
- [什麼是 「 訊號提供者 」 ？](https://sofinx.gitbook.io/sofinx-help-center-zh/bang-zhu-zhong-xin/faq/shen-mo-shi-xun-hao-ti-gong-zhe.md)
- [什麼是SOF？](https://sofinx.gitbook.io/sofinx-help-center-zh/bang-zhu-zhong-xin/qi-cheng-sofinx/shen-mo-shi-sof.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://sofinx.gitbook.io/sofinx-help-center-zh/bang-zhu-zhong-xin/faq/shen-mo-shi-zui-xiao-shou-shu.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://sofinx.gitbook.io/sofinx-help-center-zh/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://sofinx.gitbook.io/sofinx-help-center-zh/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., `/sofinx-help-center-zh/bang-zhu-zhong-xin/faq/shen-mo-shi-zui-xiao-shou-shu.md`).

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