chatcrawler.link valid

ChatCrawler

ChatCrawler is a search engine for public Telegram. It discovers public groups and channels, crawls their open feeds through the official Telegram API and makes them findable — the way a web search engine does for websites. Every venue (group or channel) has a public archive; every post has its own permanent URL.

For agents: Search engine for public Telegram groups and channels, indexing their open feeds via the Telegram API with per-venue archives and permanent post URLs.

telegram searchpublic channelstelegram groupsmessage archivepost search

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T13:30:18.335Z. Cached copy · Source on chatcrawler.link

# ChatCrawler

> ChatCrawler is a search engine for public Telegram. It discovers public groups and channels, crawls their open feeds through the official Telegram API and makes them findable — the way a web search engine does for websites. Every venue (group or channel) has a public archive; every post has its own permanent URL.

Archive pages are server-rendered HTML: no JavaScript is needed to read any of them. All times are UTC.

## How the archive is organised

- Venue card: `https://chatcrawler.link/v/{username or id}` — title, description, members, username history, archive by month.
- Latest posts: `https://chatcrawler.link/v/{ref}/m` — the newest 25 posts; older ones via `?p=1`, `?p=2`, …
- Month: `https://chatcrawler.link/v/{ref}/m?ym=YYYY-MM` — calendar of the month with the number of posts per day.
- Day: `https://chatcrawler.link/v/{ref}/m?d=YYYY-MM-DD` — every post of that day, 100 per page (`&p=1`, `&p=2`, … on busy days).
- Post: `https://chatcrawler.link/v/{ref}/m/{message_id}` — one post with its date, author and reply context; links to its day.

Any day of any venue is three links away from the venue card: card → month → day.

## Catalog and statistics

- Catalog hub: `https://chatcrawler.link/c` — rankings, topics, languages. Channels only: `https://chatcrawler.link/c/channels`; groups only: `https://chatcrawler.link/c/groups`.
- Topic: `https://chatcrawler.link/c/{topic}`, by venue type: `https://chatcrawler.link/c/{topic}/groups`, `https://chatcrawler.link/c/{topic}/channels`.
- Language: `https://chatcrawler.link/c/lang/{code}`; language × topic: `https://chatcrawler.link/c/lang/{code}/{topic}` (optionally `/groups` or `/channels`).
- Rankings: `https://chatcrawler.link/c/top/{metric}` — score, members, growth, active, views, er, cited, authors, new.
- Venue statistics: `https://chatcrawler.link/v/{ref}/stats` — subscribers history, activity, reach and ER, posting hours, top posts, who cites the venue.
- Methodology — every formula and threshold behind the numbers: `https://chatcrawler.link/methodology`.
- Venue pages open with a one-line verdict computed from those numbers; "no data" means we could not count, zero means we counted and found nothing. Posts that a channel publishes as itself are not part of the index, so reach and ER exist only where the channel's posts are indexed.

## Venue search

- `https://chatcrawler.link/c/search?q=...` — find public channels and groups by title, @username or a word from the description, with filters: `kind=channel|group`, `lang={language}`, `topic={topic}`, `size=s|m|l|xl` (audience size), `act=active`, `fresh=7d|30d` (last message), `sort=rel|members|growth|act|fresh`, `page=N`. Search result pages are not meant to be indexed.

## Discovery

- [Sitemap index](https://chatcrawler.link/sitemap.xml): venue cards, feeds, statistics, month archives and catalog pages
- [Catalog of venues by topic](https://chatcrawler.link/c)
- [How the numbers are counted](https://chatcrawler.link/methodo
…

Related sites

Other listed sites in Community. See the whole category →

Machine-readable: GET /v1/resolve?q=chatcrawler.link · GET /v1/domain/chatcrawler.link · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for chatcrawler.link:
1. POST https://agentwebmap.com/v1/sites/chatcrawler.link/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://chatcrawler.link/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/chatcrawler.link/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/chatcrawler.link).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.