ToolVet
81trust / 100

Telegram Search

by glim.sh in Search & web

x402 APIPassing, checked 4 h ago

Search Telegram: channel discovery by topic plus indexed public posts

POST
https://glim.sh/api/v1/telegram/search
Price
$0.01
per call in USDC
Uptime
100%
last 30 days
Response time
195 ms
342 ms slowest 5%
Last check
Passed
4 h ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed · Watch with other listings

How to call it

POST https://glim.sh/api/v1/telegram/search

Each call costs $0.01 in USDC on Base, paid with the request over x402.

Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.

Example request

From the listing.

POST https://glim.sh/api/v1/telegram/search
content-type: application/json

{
  "query": "solana trading"
}

Parameters

ParameterTypeRequiredDescription
kindstringNo'channels': directory lookup of channels by name/topic. 'posts': indexed t.me post pages. 'all': both. One of: all, channels, posts. Default: "all".
querystringYesSearch query

Example response

The provider's example. We can't check it without paying.

{
  "channels": [
    {
      "handle": "solana_blockchain",
      "title": "Solana"
    }
  ],
  "count": 12,
  "posts": [
    {
      "title": "...",
      "url": "https://t.me/s/..."
    }
  ]
}

Call it from code

The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.01.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://glim.sh/api/v1/telegram/search' \
  -H 'content-type: application/json' \
  --data-raw '{"query":"solana trading"}'

# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - -X POST 'https://glim.sh/api/v1/telegram/search' \
  -H 'content-type: application/json' \
  --data-raw '{"query":"solana trading"}' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

// Pays at most $0.01 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);

// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.01 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fglim.sh%2Fapi%2Fv1%2Ftelegram%2Fsearch&method=POST
const res = await pay("https://glim.sh/api/v1/telegram/search", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "query": "solana trading"
  }),
});
console.log(res.status, await res.text());
Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client

# Pays at most $0.01 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.post(
        "https://glim.sh/api/v1/telegram/search",
        json={
            "query": "solana trading",
        },
    )
    print(res.status_code, res.text)

Security scan

No findings

We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTimePrice
4 h agoPassed402155 ms$0.01
9 h agoPassed402114 ms$0.01
14 h agoPassed402217 ms$0.01
18 h agoPassed402253 ms$0.01
23 h agoPassed402335 ms$0.01
Show 10 older checks
27 h agoPassed402222 ms$0.01
31 h agoPassed402223 ms$0.01
35 h agoPassed402266 ms$0.01
39 h agoPassed402143 ms$0.01
44 h agoPassed402239 ms$0.01
2 days agoPassed402117 ms$0.01
2 days agoPassed402154 ms$0.01
2 days agoPassed402231 ms$0.01
3 days agoPassed402147 ms$0.01
3 days agoPassed402342 ms$0.01