# glim.sh Telegram Search

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

Search Telegram by topic to discover public channels and/or retrieve indexed public posts matching a query

## Facts

- Endpoint: POST https://glim.sh/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-30df38cb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_0Pu1g5SD_KlTWyOyGmOjZ

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-30df38cb -d '<json body>'
```

Example prompt: Search Telegram for public channels and posts about decentralized finance — find both relevant channels by topic and indexed posts mentioning 'DeFi'.

## When to prefer this

Use this endpoint when you need to discover public Telegram channels by topic or retrieve indexed public Telegram post content. It is purpose-built for Telegram and supports both channel directory lookup and post search in one call, unlike generic web search tools that may miss Telegram-specific content.

## Known failure modes

- Empty results if query is too niche or no indexed content exists for the topic
- Query too long (exceeds 500 character limit) returns validation error
- Telegram channels or posts may be out of date if the index has not been recently refreshed
- Private or restricted Telegram channels/posts are not accessible
- Ambiguous queries may return loosely related channels or posts

## How this service works

Search Telegram: channel discovery by topic plus indexed public posts

## Output

Returns matching Telegram channels (with names, topics, and metadata from a channel directory) and/or indexed public post pages from t.me, depending on the 'kind' parameter. Results include channel discovery data and/or post snippets relevant to the search query.

## 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-30df38cb/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from glim.sh](https://www.zero.xyz/host/glim.sh/llms.txt)
