# DeepTrawler Telegram Public Post Search

> DeepTrawler Telegram Public Post Search is a paid API for AI agents from deeptrawler.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-16).

Search public Telegram messages and posts in real time using a keyword query, returning paginated results with message metadata.

## Facts

- Endpoint: GET https://deeptrawler.com/v1/telegram/search/public-posts
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/deeptrawler-telegram-public-post-search-faf0d493
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_6yacYCYwqTDci-1RviyL4

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 deeptrawler-telegram-public-post-search-faf0d493
```

Example prompt: Search Telegram public posts for 'Bitcoin ETF' and give me the top 20 results — I want to see which channels are talking about it right now, with view counts and timestamps.

## When to prefer this

Choose this endpoint when you need real-time, unauthenticated, pay-per-call search across public Telegram posts without managing API keys or subscriptions. It is ideal for agents that need to search Telegram specifically (not Reddit, Twitter, or other platforms), require live indexing of the 'deep conversation layer', and need structured metadata like view counts, forward counts, and verified channel status. Prefer it over scraping solutions when you need clean structured output and pagination support.

## Known failure modes

- Missing or empty 'q'/'query' parameter returns an error since it is required
- Providing both 'q' and 'query' simultaneously may cause ambiguity or conflict
- Invalid cursor token from a different session or expired token may return an error or empty results
- limit values outside 1–100 are rejected by schema validation
- No results found for obscure or very specific queries returns an empty results array
- Rate limiting or payment failure (x402/MPP) results in payment-required or access-denied responses
- Telegram platform outages or indexing delays may cause stale or missing results

## How this service works

Live, multi-platform search API for the deep conversation layer. Pay per call with x402 or MPP — no API keys, no signup.

## Output

A JSON object containing the original query string, platform identifier ('telegram'), an array of matching message objects (each with a composite ID, direct URL, chat info including title/username/verified status, message text, view count, forward count, ISO-8601 timestamp, and message type), plus an opaque next_cursor string for pagination (null if no further pages), and a meta field with ordering info.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [],
     "properties": {
      "q": {
       "type": "string",
       "description": "Telegram search query (alias: query). Required."
      },
      "limit": {
       "type": "integer",
       "default": 20,
       "maximum": 100,
       "minimum": 1
      },
      "query": {
       "type": "string",
       "description": "Alias of 'q'; provide one of the two."
      },
      "cursor": {
       "type": "string",
       "description": "Opaque continuation token from a previous response's next_cursor."
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "meta": {
   "order": "telegram"
  },
  "query": "coffee",
  "results": [
   {
    "id": "-1001234567890:842",
    "url": "https://t.me/somechannel/842",
    "chat": {
     "id": "-1001234567890",
     "title": "Some Channel",
     "username": "somechannel",
     "verified": false
    },
    "text": "Coffee prices are changing...",
    "views": 15200,
    "forwards": 48,
    "timestamp": "2026-07-07T10:30:00Z",
    "message_id": 842,
    "message_type": "photo"
   }
  ],
  "platform": "telegram",
  "next_cursor": "eyJ2Ijox..."
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/deeptrawler-telegram-public-post-search-faf0d493/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from deeptrawler.com](https://www.zero.xyz/host/deeptrawler.com/llms.txt)