# glim.sh Telegram Channel & Post Fetcher

> glim.sh Telegram Channel & Post Fetcher is a paid API for AI agents from surf.cascade.fyi, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-14).

Fetches posts and discussion comments from public Telegram channels or individual posts by channel handle, URL, or post ID

## Facts

- Endpoint: POST https://surf.cascade.fyi/api/v1/telegram/get
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/glim-sh-telegram-channel-post-fetcher-b8543f28
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_K8eg6QgWwDNnR7UH4cAFK

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-channel-post-fetcher-b8543f28 -d '<json body>'
```

Example prompt: Pull the last 30 posts from the Telegram channel @durov and show me any posts mentioning 'privacy' — just the text and view counts.

## When to prefer this

Choose this endpoint when you need live, structured data from public Telegram channels or posts without setting up a Telegram Bot API key or managing a scraping stack. It is ideal for reading channel feeds, fetching individual posts with comments, searching channel history by keyword, and paginating through message archives — all with a simple pay-per-call model. Prefer it over raw Telegram Bot API integrations when you want zero-setup access and are working within an agent that supports x402 micropayments.

## Known failure modes

- Channel is private or restricted — endpoint cannot access non-public channels
- Invalid or malformed ref (bad handle format or non-existent channel) returns an error
- Discussion comments unavailable for many channels where the discussion group is not exposed on the public web preview
- Rate limits or upstream Telegram throttling may cause partial or empty responses
- Very large channels with sparse history may require many paginated calls to reach older posts

## 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

Returns a JSON object with kind ('channel' or 'post'), an array of posts each containing ID, text, and view count, channel metadata (handle and subscriber count), and pagination fields (has_more, next_cursor) for walking through history. For post refs, also includes discussion comments when available.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "ref": {
   "type": "string",
   "maxLength": 2048,
   "minLength": 1,
   "description": "Public channel ref (@handle, handle, or t.me URL) returns the channel feed; a post ref (t.me/<channel>/<id> or '<channel>/<id>') returns that post with its discussion comments."
  },
  "after": {
   "type": "string",
   "maxLength": 20,
   "description": "Return posts newer than this message id"
  },
  "limit": {
   "type": "integer",
   "default": 20,
   "maximum": 100,
   "minimum": 1,
   "description": "Max posts for channel refs (walks history pages as needed)"
  },
  "query": {
   "type": "string",
   "maxLength": 500,
   "description": "Search within the channel's full history (channel refs only)"
  },
  "before": {
   "type": "string",
   "maxLength": 20,
   "description": "Return posts older than this message id (pagination cursor from next_cursor)"
  },
  "comment": {
   "type": "string",
   "maxLength": 20,
   "description": "Post refs: center the comment window on this comment id (walks older comments)"
  },
  "include_comments": {
   "type": "boolean",
   "default": true,
   "description": "Post refs: include discussion comments. Telegram's public embed serves a small window of the most recent comments; walk older ones by re-calling with comment=<oldest returned comment id>. Availability varies by channel - many discussion groups are not exposed on the public web preview."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "kind": "channel",
  "posts": [
   {
    "id": "durov/530",
    "text": "...",
    "views": 4060000
   }
  ],
  "channel": {
   "handle": "durov",
   "subscribers": 11700000
  },
  "has_more": true,
  "next_cursor": "510"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/glim-sh-telegram-channel-post-fetcher-b8543f28/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)