Telegram Bot Search — Find Bots by Task
Pricing
from $2.00 / 1,000 bots
Telegram Bot Search — Find Bots by Task
Find Telegram bots by what they do. Export descriptions, known commands, language and links. This is catalog discovery; current bot responsiveness is explicitly not checked.
Pricing
from $2.00 / 1,000 bots
Rating
0.0
(0)
Developer
TGDen — Telegram Intelligence
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
12 hours ago
Last modified
Categories
Share
Find bots for a task and export descriptions, known commands and Telegram links.
Part of TGDen — Telegram Intelligence. No Telegram account, phone number or session is required.
Try it
Use this input, run the Actor and open its dataset (JSON, CSV or the table view):
{"queries": ["group moderation"],"maxBotsPerQuery": 5}
Real output
A shortened row read on 23 October 2026 during owner-account acceptance testing. Results change as the corpus changes.
[{"username": "chatzillabot","name": "ChatZilla | Group Moderation","url": "https://t.me/chatzillabot","description": "🛡 <b>ChatZilla</b> — the moderation bot for your groups.","language": "en","commands": ["start","language","miniapp"],"status": "not_checked","firstSeenAt": "2026-06-11T05:24:15.055349Z"}]
The dataset contains the delivered rows. The run's OUTPUT record adds counts, an explicit outcome (results, valid_zero_result, limited or incomplete), source timings and any stop reason. A source failure fails the run; it is never presented as a successful empty search.
Cost
$0.005 per run start + $0.002 per bot delivered. With the 256 MB memory limit there is one start event. Ten billable results cost about $0.025 in Actor fees. Zero matches incur only the start fee. Prices and any platform charges shown by Apify at launch are authoritative.
Set Maximum charge per run before starting (default $0.50). Delivery stops when the remaining budget cannot pay for another result; duplicate results are not billed twice in a run. Apify free-plan accounts receive at most 50 billable results per run. The amount of data in a snapshot may be larger than your budget permits.
Freshness and interpretation
Results come from an existing catalog, not a live Telegram check. Use each audience or signal measurement timestamp. Some observations can be weeks old; null means unmeasured. Coverage and matches vary by topic and language.
Bot responsiveness is not checked. status=not_checked is intentional. firstSeenAt is when the catalog discovered a bot, not a recent uptime check. Description language and task matches are inferred.
Why use it
Search a task and get structured bot descriptions and commands without setting up a Telegram client.
This Actor reads public catalog data. It does not join groups, send messages or contact anyone. Verify the source and suitability before outreach or business decisions.
Watch an example

API and scheduled runs
Use the same JSON input with the public Actor API. Keep your Apify token in an environment variable.
curl -X POST \-H "Authorization: Bearer $APIFY_TOKEN" \-H "Content-Type: application/json" \--data @input.json \"https://api.apify.com/v2/acts/telegrambest~telegram-bot-finder/run-sync-get-dataset-items?memory=256&timeout=180&maxTotalChargeUsd=0.50"
For longer runs use Apify's asynchronous run endpoint and fetch the dataset after completion. Where available, onlyNew=true remembers delivered items for this Actor and your account so scheduled searches skip them. Keep it off when you want a full repeatable snapshot.
The family
Buyer Search · Groups · Similar Groups · Channels · Bots · Username Checker · Marketplace Ads · Prices · Demand Map
Questions or a bad result? Open an issue on this Actor and include the run link and expected behavior. Never post tokens or Telegram sessions.