x402base-sepoliaquality 0.25

x402-payable Telegram messaging agent on Base Sepolia, powered by Questflow.

Price
0.1 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint exposes a Questflow-hosted AI agent that provides Telegram messaging and notification capabilities, accessible via the x402 payment protocol. The agent accepts a text message as input and returns a text response, enabling programmatic interaction with Telegram-related functionality from both web2 and web3 applications.

Payment is handled via x402 on the Base Sepolia testnet using USDC (asset 0x036CbD53842c5426634e7929541eC2318f3dCF7e), with a maximum cost of 100,000 units per request (likely 0.10 USDC given 6-decimal USDC). The endpoint is a simple POST that takes a JSON body with an "input" string field and returns a "response" string field. The maximum timeout per request is 1,200 seconds (20 minutes).

Documentation is minimal — there is no OpenAPI spec, no dedicated docs page, and no detailed description of what Telegram operations the agent actually performs (e.g., sending messages, reading channels, managing bots). The parent platform, Questflow, focuses on autonomous AI agents for onchain markets and trading, but this particular agent is described only as a "Telegram connector." Because the endpoint runs on Base Sepolia (a testnet), it is likely intended for development and testing rather than production use.

Capabilities

telegram-messagingx402-paymentbase-sepolia-usdcai-agentreal-time-notificationspost-json-api

Use cases

  • Sending or receiving Telegram messages programmatically via an AI agent
  • Integrating Telegram notifications into web3 workflows with micropayments
  • Testing x402-based agent-to-agent communication on Base Sepolia

Fit

Best for

  • Developers experimenting with x402 payment-gated APIs
  • Web3 apps needing Telegram notification integration
  • Agent-to-agent messaging workflows on testnet

Not for

  • Production-grade Telegram bots (testnet only)
  • High-throughput messaging with sub-second latency (20-min timeout ceiling)
  • Users who need detailed API documentation or guaranteed SLAs

Quick start

curl -X POST \
  https://api-dev.intra-tls2.dctx.link/x402/agent/qrn:agent:68230447d973977d61d66ce1 \
  -H 'Content-Type: application/json' \
  -H 'X-PAYMENT: <x402_payment_header>' \
  -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 to0x0A2C9c2A295673B5B355735Cbd03f7bD815D8569
CurrencyUSDC

Quality

0.25/ 1.00

No OpenAPI spec, no docs endpoint, no usage examples, and the endpoint runs on a testnet. The only concrete information comes from the x402 challenge payload, which provides a minimal input/output schema and payment details. The response example is entirely inferred.

Warnings

  • Endpoint is on Base Sepolia testnet — not suitable for production use
  • No OpenAPI or dedicated documentation available
  • Exact Telegram capabilities (send, read, manage) are unspecified
  • Response example is inferred; no real sample response was available
  • maxAmountRequired of 100000 units — actual USD cost depends on token decimals (likely $0.10 USDC)

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-18 18:53:12Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-22

Agent access