# glim.sh Telegram Search

> glim.sh Telegram Search is a paid API for AI agents from surf.cascade.fyi, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Search Telegram channels and posts by query, returning matching channel directories and indexed post pages from t.me

## Facts

- Endpoint: POST https://surf.cascade.fyi/api/v1/telegram/search
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/glim-sh-telegram-search-c1583e33
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_G-1ljeXc0p83051q3RTwK

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability glim-sh-telegram-search-c1583e33 -d '<json body>'
```

Example prompt: Search Telegram for channels and posts about 'DeFi lending protocols' — I want to find both relevant communities and recent post pages on the topic.

## When to prefer this

Use this endpoint when you need to discover Telegram channels by topic or find indexed Telegram post pages without managing API keys or a scraping stack. It is ideal for agents that need live Telegram data on-demand with per-call pay-as-you-go pricing via x402. Prefer this over building a custom Telegram scraper or using the official Telegram Bot API when you want simple keyword-based channel and post discovery.

## Known failure modes

- Query too short or empty — returns validation error
- No matching channels or posts found — returns empty arrays with count 0
- Telegram indexing lag — recently created channels or posts may not appear
- Rate limiting or payment failure — 402 response if payment not attached correctly
- Query exceeds 500 character limit — returns input validation error

## How this service works

One remote endpoint gives your agent live data from Twitter, Reddit, the open web, GitHub and more. No API keys, no scraping stack - just connect the URL and go.

## Output

A JSON object containing a count of total results, an array of matching Telegram channels (each with a title and handle), and an array of matching indexed t.me post pages (each with a URL and title).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "kind": {
   "enum": [
    "all",
    "channels",
    "posts"
   ],
   "type": "string",
   "default": "all",
   "description": "'channels': directory lookup of channels by name/topic. 'posts': indexed t.me post pages. 'all': both."
  },
  "query": {
   "type": "string",
   "maxLength": 500,
   "minLength": 1,
   "description": "Search query"
  }
 }
}
```

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/glim-sh-telegram-search-c1583e33/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from surf.cascade.fyi](https://www.zero.xyz/host/surf.cascade.fyi/llms.txt)