> For the complete documentation index, see [llms.txt](https://docs.gmgn.ai/cn/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gmgn.ai/cn/yao-qing-gmgnaibot.md).
# 邀请 @GMGNAI\_BOT
## **1. 邀请 群组合约查询机器人 加入你的群组**
**@GMGNAI\_BOT**
**快速邀请** 👉🏻 [单击此处邀请@GMGNAI\_bot加入你的 Telegram 群组](https://t.me/GMGNAI_bot?startgroup=true)
**机器人描述：**
1）查看代币分析：任何人都可以向群组发送**代币合约地址**，机器人会自动回复代币价格、资金池流动性、内幕人员等代币分析数据。
2）查看钱包盈亏分析：任何人都可以向群组发送**钱包地址**（仅限 Solana），机器人会自动回复钱包分析，例如 7d 盈亏、已实现利润、未实现利润、胜率、持有代币分析、最近 5 笔交易。
支持的公链： ETH, Solana, Base, BSC
## 2. 授予机器人管理员权限
## 3. 发送/set命令更改语言
发送 /set 命令以更改语言。
## 4. 配置带有返佣代码的链接
* **获取 Telegram 群组 ID：**将机器人添加到组并授予其管理员权限后，向组发送 /groupid 命令并复制组 ID（以负号开头的一串数字，以 -1 或 -4 开头，如 -1xxxxxxxxxxxx 或 -4xxxxxxxxx）。
* **配置返佣代码：** 请填写Google申请表，并在备注中包含社群ID：
💡 **在此处生成你的返佣代码（总共 3 个代码）：**
> Solana 网站
>
> ETH 网站
>
> GMGN狙击机器人[@GMGN\_sol\_bot](https://t.me/GMGN_sol_bot)
## **5. 🎉 配置成功**
你邀请的交易量越多，你的佣金比例就越高（[申请增加佣金比例](https://forms.gle/EhofPCZ1g9fXaA6S7))
---
# 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://docs.gmgn.ai/cn/yao-qing-gmgnaibot.md?ask=&goal=
```
`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.