Publish, sync, subscribe.
How fansub groups apply and publish, how viewers automate downloads with RSS, how developers call the API. Every page describes what production actually does.
AniBT Wiki is written for three people: the fansub group shipping a release, the viewer whose downloader should keep up, and the developer wiring AniBT into a script. When behaviour changes, the docs change; the changelog is dated.
# Read endpoints need no auth curl https://anibt.net/api/seasons/anime { "ok": true, "data": { "currentSeason": "2026夏", "total": 91, "byWeekday": [{ "weekdayLabel": "周一", "animes": [{ "bgmId": 646464, "hasRelease": true, … }] }, …] } }
Publish once, sync to six sites
Credentials and failure handling: one page per site.
Subscribe once, follow to the end
By show, by fansub group, site-wide, or everything you follow.
Public tracker
https://tracker.anibt.net/announceAdd it when you create the torrent. AniBT releases are whitelisted automatically.
For LLMs and agents
Plain-text entry points, ready to feed a model.
/llms.txt# full text
/llms-full.en.txt# one page as Markdown
/en/docs/apply.md# API contract
/openapi.yaml
Fansub toolbox
What you need besides publishing.
Recent changes
Dated entries for viewers and fansub groups.
Sonarr, Radarr, and Prowlarr can add https://anibt.net/torznab as a Torznab indexer to search and grab anime releases directly.
The status page now shows 30-, 60-, and 90-minute announce, peer, torrent, completion, and connection history.
/about now opens with a one-line positioning statement, this season's real numbers, where a publish goes, the groups that publish here, and the sibling projects.