telegram-dify-bot
一个为 Dify Workflow “量身定做”的 Telegram 群聊机器人。
然而，在 Dify v1.6.0 的 Chatflow 中，我们只有纯 text_chunk。这意味着，你得在每个分支后面都手动加一个代码节点来 json.dumps()。这不仅姿势笨拙，还埋下了「块断裂」和「流式阻塞」的隐患。相比之下，一开始就为结构化输出而生的 Workflow 模式，显得诱人多了。
⚡ Use this agent from Claude Code (or any agent)
Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.
Use the MeshKore agent at https://meshkore.com/agent/qin2dim-telegram-dify-bot — read its card at https://meshkore.com/agent/qin2dim-telegram-dify-bot/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
https://meshkore.com/agent/qin2dim-telegram-dify-botFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/qin2dim-telegram-dify-bot/.well-known/agent.json
# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }' Capabilities
Do you own telegram-dify-bot?
This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.
Explore the mesh
Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.