EZTV
- Free allowance
- No key and no account: /api/get-torrents?limit=3 returned JSON reporting torrents_count 1,095,199 with magnet_url and filename per row.
- Verdict
- ★ qualifiesusable as stated; the read path was probed
- Cost
- free tier
- Identity
- anonymousno card, no phone
- Binding limit
- request-ratenone published; the call answered immediately with Cache-Control no-store, so nothing suggests an edge cache is absorbing repeats
- Evidence
- documented2 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-11-23checked 2026-10-23 (live); stale on 2026-11-23
| Free tier | No key and no account: /api/get-torrents?limit=3 returned JSON reporting torrents_count 1,095,199 with magnet_url and filename per row. unit requests; metered on request-count |
|---|---|
| Price | USD 0 |
| Limits |
No rate headers were returned on the call made. The API is undocumented beyond community use, so the schema is the risk rather than the quota. |
| Binding | request-rate An index has no byte quota; the request rate is the only lever, and the page parameter lets a client pace a backfill deliberately. |
| Identity | anonymous No key and no account on the API call made today. |
| Egress | no byte allowance: JSON and magnets only free allowance: none published |
| Per-object cap | not applicable: index rows |
| Retention | the API returns the catalogue history, so old episodes stay listed after the swarm empties |
| Interface | rest GET /api/get-torrents with limit and page parameters returns JSON. Also /api/get-torrent?limit=... per-page variants and an HTML front end. endpoint: https://eztv.re/api/get-torrents?limit=3 |
| Tooling | One GET; the magnet_url field means no torrent file fetch is needed. |
| Composes with | Pull the recent page once a day, filter by show, and hand the magnet to a debrid service; the API's page parameter is the cursor for a backfill. |
| Reliability | The magnet dn strings carry a different domain ('[EZTVx.to]') from the host that answered (eztv.re), so a client that whitelists one will meet the other. Cache-Control is no-store, so repeats reach the origin. |
| Notes | The largest no-account magnet feed measured here by row count (1.09 million), and the narrowest by subject. It pairs with the DDL feeds badly (TV only) and with Torrentio well, because Torrentio already indexes it. |
| Evidence note | documented The API was called on 2026-10-23 and the JSON read. A recorded backfill would raise it to measured and would show whether page depth is capped. |
| Parsed numbers |
|
Evidence 2
| date | source | what it proved |
|---|---|---|
| 2026-10-23 | eztv.re/api/get-torrents?limit=3 | HTTP 200 JSON with torrents_count 1,095,199, limit 3, page 1, and rows carrying magnet_url with dn and multiple udp trackers |
| 2026-10-23 | eztv.re/api/get-torrents?limit=3 | response header Cache-Control: no-store, so repeats reach the origin rather than an edge cache |
More fields 3
| torrents count | 1095199 |
|---|---|
| protocol | rest-json |
| subject | tv |