Quirox Telegram Bot Backend

Created By
Himank-Ja year ago
This repo demonstrates how to build a telegram bot using SSE Server and implement agentic flow using MCP with tools like Gmail, GDrive
Overview

What is Quirox Telegram Bot?

Quirox Telegram Bot is a backend service that enables the creation of a Telegram bot powered by an AI agent, capable of interacting with various tools such as Google Sheets and web search.

How to use Quirox Telegram Bot?

To use the Quirox Telegram Bot, clone the repository, set up the required environment variables, and run the MCP server alongside the FastAPI application to interact with the AI agent via HTTP requests.

Key features of Quirox Telegram Bot?

  • AI Agent: Utilizes Google Gemini for reasoning and task execution.
  • Tool Integration: Integrates with Google Sheets for data management and DuckDuckGo for web searches.
  • FastAPI Interface: Provides a web server for chat interactions with the AI agent.

Use cases of Quirox Telegram Bot?

  1. Automating data entry and management in Google Sheets.
  2. Conducting web searches and fetching content directly through Telegram.
  3. Enhancing user interaction with automated responses and task execution.

FAQ from Quirox Telegram Bot?

  • Can Quirox Telegram Bot handle multiple tasks simultaneously?

Yes! The bot can manage multiple requests and tasks through its integrated tools.

  • Is there a limit to the number of Google Sheets it can manage?

No, as long as the Google API limits are respected, it can manage multiple sheets.

  • How do I set up the Google API credentials?

Follow the setup instructions in the repository to create a service account or use OAuth for authentication.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Himank-J
Star
0
Language
Python
License
-

Recommend Servers

View All
Voyei

3 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

14 hours ago