Magnet Link Downloader
t.me · Debrid · 1 record · JSON
Magnet Link Downloader (@MagnetLinkDLBot) Debrid
caveatany-phoneno cardphoneR
| Free tier | The bot's own profile is its whole offer: "Magnet Link Downloader" and "If not working then Try @MagnetLinkDL2Bot". No price, byte allowance or daily count is published anywhere on the preview page. unit none; metered on none; Free by default: no payment surface is reachable from the bot's page, and a paid tier that is not advertised is not a tier a client can buy. |
|---|---|
| Price | USD 0 |
| Per-object cap | Not stated. |
| Retention | Not stated. The output is a link to a file held on the operator's seedbox; how long it survives is unpublished. |
| Egress | The bot resolves a torrent and serves the result as an HTTP link. No bandwidth terms, allowance or price is published. |
| Identity | any-phone A Telegram account, so any phone number that can receive a code. No email, payment or document is asked for. |
| Limits |
Nothing is published. |
| Binding | none No counter is published, so none can be named; what a client meets is a queue on a shared bot, and that is an availability limit rather than a quota. Recording 'none' here is a statement about the published record, not a claim that the bot is unlimited. |
| Interface | unknown A Telegram bot only. There is no HTTP endpoint: the interface is a chat with @MagnetLinkDLBot, and the operator publishes a fallback bot (@MagnetLinkDL2Bot) rather than an API. |
| Tooling | Telegram client. Automating it means a Telegram user session against a third-party bot, which is the opposite of the programmatic access this corpus prefers. |
| Composes with | The cheapest known conversion from a torrent to an HTTP link with no client, no disk and no seeding: a magnet goes in, a link comes out, and the download happens elsewhere. It is the debrid function reduced to one chat, with no published capacity behind it. |
| Reliability | The operator runs a spare bot for when the main one breaks, which is an honest statement about uptime. A third-party bot sees every magnet a client submits, and the resulting link is served from infrastructure nobody in this corpus controls. |
| Notes | Recorded as a service because it resolves and fetches: the client supplies a magnet and receives a link to bytes. The ledger's account-mirror bots (for example anything that clones into a user's own Drive) are excluded by that same test and listed in findings.md instead. |
| Evidence rung | reported The service's existence and function come from its own Telegram profile, which is its operator's claim. No magnet was submitted, so neither the conversion nor any speed is measured. Moving up needs one torrent run end to end. |
| Checked | 2026-10-24 (live); stale on 2026-11-07 |
| Parsed numbers |
|
Evidence (2)
| date | source | what it proved |
|---|---|---|
| 2026-10-23 | t.me/MagnetLinkDLBot | the bot is live and self-described as 'Magnet Link Downloader', with a named fallback @MagnetLinkDL2Bot and a support channel @TheNiceBots |
| 2026-10-23 | t.me/TheNiceBots | the support channel exists with 140,687 subscribers and lists the operator's other bots, which is the scale signal for the queue behind this one |
More fields (1)
{
"fallback_bot": "@MagnetLinkDL2Bot"
}Unknown or withheld values (1)
$.interfaceinterface-unknown