DiegoG.TelegramBot
A Library to simplify Bot Command building and Conversation definition
In order to make use of most of its qualities, two main points are required: Declaring a command (further explain below) and utilizing the MessageQueue The simplest way to use the MessageQueue is to make use of the two methods in TelegramBotCommandClient that interact directly with it, namely void QueueBotAction(BotAction action) and Task QueueBotFunc(BotFunc func) Both queue a task to the MessageQueue to be issued to the telegram API when the Queue deems it fit.
⚡ 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/diegog1019-diegogtelegrambot — read its card at https://meshkore.com/agent/diegog1019-diegogtelegrambot/.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/diegog1019-diegogtelegrambotFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/diegog1019-diegogtelegrambot/.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 DiegoG.TelegramBot?
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.