> For the complete documentation index, see [llms.txt](https://docs.frontrun.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.frontrun.pro/cn/chan-pin-gong-neng/10-wan-+-yu-zhi-di-zhi-biao-qian.md).
# 10 万+ 预置地址标签
机构级地址目录，收录 10 万多个已标记钱包——涵盖 KOL、基金、内部人士与聪明钱追踪地址——在任何页面内即时呈现其动向。
当知名交易者触碰某个代币，你能第一时间看到。我们不断扩充的钱包标签库，会在你浏览的每个界面同步显示。
你的自定义标签可在包括 Solscan、Axiom、Photon、GMGN 在内的所有主流平台间无缝同步。
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.frontrun.pro/cn/chan-pin-gong-neng/10-wan-+-yu-zhi-di-zhi-biao-qian.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
