> For the complete documentation index, see [llms.txt](https://docs.bao.la/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bao.la/he-xin-gong-neng/kol-xiang-qing.md).
# KOL详情
#### 1、个人资料与平台来源
页面顶部展示 KOL 的头像、昵称、账号、个人简介及平台来源标识，并提供关联 X 账号的访问入口，方便用户确认账号身份及内容来源同时提供备注功能，用户可以按自己的习惯标记账号，方便识别和管理长期关注的对象。
#### 2、盈利 Top 5
集中展示该账号盈利表现突出的五个代币，包括代币名称、盈利金额及收益率，让用户快速了解其代表性交易。通过这些案例，可以发现值得进一步研究的资产，并结合完整持仓和历史交易，了解盈利来源与交易特点。该区域展示的是部分盈利案例，不能替代整体业绩分析。
#### 3、资产概览与变化趋势
“资产”视图展示总资产、持仓价值、可用现金及资产变化图表，帮助用户了解账号当前的资金规模和资产构成。支持切换 24 小时、7 天、30 天等观察窗口，比较不同时间范围内的资产变化。
#### 4、个人喊单信息流
右侧“喊单”信息流汇集该账号发布的代币观点，展示发布时间、来源平台、正文及关联代币。代币卡片提供喊单时市值、可获取的持仓和盈亏信息，部分卡片还展示近 24 小时的 KOL 喊单与买入统计。
#### 5、个人交易动态
“交易”入口用于查看账号的买卖行为，与喊单信息形成互补。用户可以分别追踪其公开表达和实际交易记录，观察关注的代币是否发生买入、卖出或仓位调整，并进一步进入代币页面查看行情与链上数据。
#### 6、持仓表现分享
持仓记录提供分享入口，方便用户围绕具体代币的持仓和收益表现进行交流。配合主页分享，可以分别分享完整账号或某个代币的表现，满足不同的讨论场景。
---
# 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.bao.la/he-xin-gong-neng/kol-xiang-qing.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.
