Scrape posts, views, reactions, media and comment counts from any public Telegram channel, plus exact subscriber counts and channel stats. Only-new-posts mode for schedules. No login or API key.
First release: posts, channel stats rows, only-new-posts monitor, crypto and link extraction, in-channel search, date and keyword filters, optional comments.
Pricing proposal (for the coordinator)
Pay per event. Keep apify-actor-start at default. Remove apify-default-dataset-item.
Event
Price
post (primary)
$0.0006
channel
$0.0015
post-comments
$0.0004
Suggested minimal max total charge: $0.50.
Measured costs
Platform build 1.0.4, default memory 1024 MB (measured 2026-11-18, usage = compute plus storage as billed by Apify, no proxy).
Run
Result
Time
Usage
Prefill (3 channels x 50)
150 posts + 3 channel rows, 0 errors
4.7 s
$0.0006
Bigger (6 channels x 500)
2,860 posts + 6 channel rows, 0 errors, 0 x 429
48.6 s
$0.0116
3x (6 channels x 1500)
6,860 posts + 6 channel rows, 0 errors
132 s
$0.0368
Comments (WatcherGuru, 100 posts)
100 posts, 100 with comments
25.7 s
$0.0021
Monitor run 1 (5 posts) / run 2 (nothing new)
5 posts + 1 channel row / 0 rows (cursor loaded from the named store with limited permissions)
2.8 s / 2.1 s
$0.0002 / $0.0002
Cost per 1,000 posts: about $0.004 to $0.005 (bigger run $0.0116 / 2.86k, 3x run $0.0368 / 6.86k). Price $0.60: under 1%.
Cost per 1,000 posts with comments: about $0.02 (one extra widget request per post).
Channel rows are one card request plus one page: about $0.01 per 1,000 (estimate, 2 requests each at 5 req/s); price $1.50.
Unchanged monitor run with 1 channel: about $0.0002 (2.1 s). 20 channels estimated about $0.001.
Memory: at 256 MB the container is CPU starved (cheerio parsing blocks the event loop): bigger run took 218 s for $0.0174. At 1024 MB it takes 48.6 s for $0.0116, so default memory is 1024 MB.
Linearity: the 3x run cost per post is about 30% above the bigger run (page fetch latency varies); still far under budget.
Platform note: Telegram answered 100% of requests with 200 from Apify platform IPs without proxy, at 5 req/s (about 350 requests, 0 x 429).