QQ official bot integration
Receive and reply to authorized messages using an official bot identity.
Models generate and reason. Agents use tools to work on tasks. A harness manages an agent’s environment. MCP connects tools and data. Skills are reusable task guidance.
Current task
QQ official bot integration
Validation
Receive and reply to authorized messages using an official bot identity.
Prerequisites
Exchange AppID/AppSecret for access_token; use QQBot authentication server-side instead of the deprecated Token.
API key
Exchange AppID/AppSecret for access_token; use QQBot authentication server-side instead of the deprecated Token.
Model / service
Local-model designs need a specific model and tool-capability checks; device connection itself does not need an LLM.
Agent / runtime
Only reviewed tools are listed; AI bridging and autonomous planning remain implementation and validation work unless explicitly documented.
Hardware
Hardware needs depend on software, model, quantization and task; no minimum or smooth-performance benchmark was run.
Permissions & risks
A local model still sends and receives through Tencent; process authorized context only and never bulk-export group chats.
API key
Exchange AppID/AppSecret for access_token; use QQBot authentication server-side instead of the deprecated Token.
Platform policy
Official bots do not take over personal QQ accounts; obey review and permissions without spam, harassment or ban bypass.
Deployment preference
The backend may be local or hosted; verify callback networking separately and leave existing bots and Tunnels unchanged.
Validation
Planned: local synthetic responses for error codes and expiry, then one permitted message and revocation after separate test credentials. Not executed.
Validation
Official documentation reviewed; this site has not run this combination or tested the device.
Limits & boundaries
Current group endpoints and event-signature documentation were not fully obtained; do not guess. Network access, costs and eligibility remain unknown.
Alternatives
If prerequisites are unmet, use a read-only or manual flow, then revalidate alternatives below without inheriting this compatibility status.
Alternatives
telegram-bot
line
discord
Cost
Not verified
Price not verified; check software, model, API, hardware and hosting costs separately.
Implementation steps
- 01Register a separate test bot using official v2 documentation and complete required platform review.
- 02Protect secrets server-side and inspect access credentials and business error codes, not HTTP status alone.
- 03Test permitted synthetic messages only; check identity, msg_id, expiry and stop behavior before adding a model.
Connection method
Not tested by BlueFish
POST https://api.bot.qq.com/app/getAppAccessTokenPOST https://api.bot.qq.com/v2/users/{user_openid}/messagesLimits & boundaries
- Current group endpoints and event-signature documentation were not fully obtained; do not guess. Network access, costs and eligibility remain unknown.
- Official documentation reviewed; this site has not run this combination or tested the device.
Permissions & risks
- A local model still sends and receives through Tencent; process authorized context only and never bulk-export group chats.
- Official bots do not take over personal QQ accounts; obey review and permissions without spam, harassment or ban bypass.
Original sources
- Tencent QQ official documentation · src-qq-v2-start ↗
bot.q.qq.com · 2026-10-16 · Official documentation
- Tencent QQ official documentation · src-qq-v2-token ↗
bot.q.qq.com · 2026-10-16 · Official documentation
- Tencent QQ official documentation · src-qq-v2-call-guide ↗
bot.q.qq.com · 2026-10-16 · Official documentation
- Tencent QQ official documentation · src-qq-v2-changelog ↗
bot.q.qq.com · 2026-10-16 · Official documentation