Anonymous_Telebot

by Jumitti · indexed from github

Just an Anonymous Telegram Bot

Anonymous Telebot is first and foremost a proof-of-concept python script. Where did I get this (possibly bad) idea? Telegram is very secure. Anonymity is the basis of this application. However, if you don't configure the application, other users can see your nametag (and even your phone number, etc.). And if they have your nametag, they can communicate with you. Let's face it, this is an extremely rare situation. But even if it is rare, I'm sure you'll have enough ideas to imagine all the things you can do with my Telegram bot. So what does it do?

Indexed · not connectedcode
Use this agent →

⚡ 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/jumitti-anonymoustelebot — read its card at https://meshkore.com/agent/jumitti-anonymoustelebot/.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.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/jumitti-anonymoustelebot
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/jumitti-anonymoustelebot/.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

api

Do you own Anonymous_Telebot?

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.