telegram-rag-bot

by Mikhail Malorod · indexed from pypi

Production-ready Telegram FAQ bot with Russian LLMs, RAG, and multi-provider fallback

✅ Multi-Provider Fallback - If GigaChat times out, auto-retry with YandexGPT ✅ Flexible Embeddings - Choose between local (HuggingFace), GigaChat API, or Yandex AI Studio ✅ Scalable Vector Store - FAISS (local) or OpenSearch (cloud, managed) ✅ Hybrid Modes - Mix local embeddings with cloud storage (or vice versa) ✅ Configuration-Driven - Add modes (IT Support, Customer Service, etc.) via YAML ✅ Token Tracking - Prometheus metrics for costs + latency ✅ Non-Blocking - Handles 1000+ concurrent users with async/await ✅ FAQ Management - /reload_faq to update knowledge base instantly ✅ Russian LLMs…

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

llmchatragaibot

Do you own telegram-rag-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.