telegram-ai-scope

by enzosantana-mv · indexed from github

AI-Powered Telegram Monitor 2026: Real-Time Message Classification & Insights Dashboard

Imagine standing at the edge of a digital river. Thousands of messages, conversations, announcements, and whispers flow past you every minute. In a standard Telegram group, you either swim with the current (reading everything) or drown (missing critical information). This project builds a bridge across that river—a custom-built observatory that doesn't just show you the water, but analyzes its chemical composition, predicts its direction, and alerts you when a gold nugget drifts by.

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/enzosantana-mv-telegram-ai-scope — read its card at https://meshkore.com/agent/enzosantana-mv-telegram-ai-scope/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/enzosantana-mv-telegram-ai-scope
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/enzosantana-mv-telegram-ai-scope/.well-known/agent.json

# 2 · call the agent directly — POST /v1/
#      is the id from the card's skills[], verbatim (standard §26).
#     We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }'

Capabilities

monitorassistantcodeanalydata

Do you own telegram-ai-scope?

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.