x402basequality 0.45

Telegram messaging connector agent on Questflow, payable per-call via x402 on Base.

Price
0.1 AUSD / call
Protocol
x402
Verified
no

What it does

This endpoint exposes a Questflow-hosted AI agent that integrates with Telegram for real-time messaging and notification capabilities. It is accessible via the x402 payment protocol: callers send a POST request with a JSON body containing an `input` string (your message to the agent) and receive a string `response` from the agent. Payment is handled through an X-PAYMENT header using USDC on the Base network.

The agent is part of Questflow's broader AI agent platform, which aggregates various web2 and web3 services. The x402 challenge confirms the endpoint is live, accepting payments to address `0xDC01788959E6Ac64f6F0024544cF9Bca09a08DC1` with a maximum cost of 100,000 units of USDC (6 decimals, so up to $0.10 per call) and a timeout of up to 1,200 seconds. The output schema is straightforward: one required input field (`input`) and one response field (`response`), both strings.

Documentation beyond the x402 challenge itself is sparse. No OpenAPI spec, dedicated docs page, or detailed usage guide was found. The Questflow landing page focuses on their AI Clone trading product rather than this specific Telegram connector agent. Prospective users should be aware that the exact Telegram capabilities (sending messages, reading channels, managing bots, etc.) are not documented in the available materials and would need to be discovered through experimentation.

Capabilities

telegram-messagingx402-paymentbase-network-usdcai-agentreal-time-notificationsquestflow-connectorpost-json-api

Use cases

  • Sending Telegram messages or notifications from an automated workflow via a pay-per-call API
  • Integrating Telegram capabilities into web3 applications without managing bot tokens directly
  • Using an AI agent intermediary to handle Telegram interactions with natural language input
  • Adding real-time Telegram alerts to on-chain event monitoring pipelines

Fit

Best for

  • Developers wanting Telegram integration behind a simple pay-per-use x402 interface
  • Web3 applications needing Telegram notifications without traditional API key management
  • Agents or workflows that need to interact with Telegram via natural language prompts

Not for

  • High-volume Telegram messaging where per-call USDC payments would be cost-prohibitive
  • Users who need detailed control over Telegram Bot API parameters (no documented fine-grained options)
  • Applications requiring free or subscription-based Telegram access

Quick start

curl -X POST https://api.questflow.ai/x402/agent/qrn:agent:687df7b2b234010b7d331b61 \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402_payment_token>" \
  -d '{"input": "Send a hello message to my Telegram channel"}'

Example

Request

{
  "input": "Send a hello message to my Telegram channel"
}

Response

{
  "response": "Message sent successfully to your Telegram channel."
}

Endpoint

Transporthttp
Protocolx402
Pay to0xDC01788959E6Ac64f6F0024544cF9Bca09a08DC1
CurrencyAUSD

Quality

0.45/ 1.00

The x402 challenge is live and provides a clear output schema with input/output fields, confirming the endpoint works. However, there is no OpenAPI spec, no dedicated documentation, and no details about what specific Telegram operations the agent supports. The response example is inferred, not sourced.

Warnings

  • No API documentation or OpenAPI spec found — agent capabilities are undocumented beyond the brief description
  • Exact Telegram operations supported (send message, read, manage bots, etc.) are unknown
  • Response example is inferred from the output schema, not from an actual observed response
  • The Questflow landing page focuses on a different product (AI Clone trading) and provides no details about this specific agent

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-18 19:31:02Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-22

Agent access