# TorrentX

> t.me | Debrid; 1 record: free tier, limits, identity cost and evidence.

HTML https://fshy.ajam.dev/p/t-me-torrentxbot/ | JSON https://fshy.ajam.dev/api/v1/entity/t-me-torrentxbot.json | how to read a record: https://fshy.ajam.dev/llms-full.txt

## TorrentX (@TorrentXbot)

- `debrid/telegram-torrentx-bot` | dead | evidence documented | binding none | category hosted bot (torrent to Google Drive) | tier free
- needs card no, phone yes, ID no, institution no | verified 2026-10-23T01:52:23.000Z (live) | stale on 2026-11-23
- url https://t.me/TorrentXbot
- free tier: Dead. t.me/TorrentXbot returns 'Telegram: Contact @Torrent' with no Start action: the username now resolves to a user account. | unit: none | metered on: none | read on: 2026-10-23 | source: [1]
- per-object cap: Not applicable: the bot is gone. | source: [2]
- retention: Not applicable: no service. | source: [1]
- egress: Not applicable. | metered: no | source: [1]
- identity: any-phone | detail: Was a Telegram account.
- interface: unknown
- limits note: No live limit exists to name.
- binding note: Nothing binds because nothing is served.
- interface detail: Was a Telegram chat bot that downloaded a torrent and uploaded it to Google Drive.
- tooling: None.
- composes with: Nothing. The surviving path for the same job is a self-run mirror bot.
- reliability: Second confirmation of the same failure: the Chinese directory already listed it under 'the following are all unusable' in 2022, and the handle is a user account today.
- notes: Do not re-open unless @Torrent is seen running as a bot.
- evidence note: Read: the page is a Contact action, not a Launch action. The 2022 directory corroborates the direction of travel.
- evidence:
  - [1] 2026-10-23: page title 'Telegram: Contact @Torrent', no Start Bot action, empty description
  - [2] 2026-10-23: post 73: '@TorrentXbot downloads and uploads to Google Drive', listed later under 'the following are all unusable'
- sources:
  - [1] https://t.me/TorrentXbot
  - [2] https://t.me/bot_zh