autobrr
autobrr is an open‑source, self‑hosted automation tool that bridges IRC announce channels and RSS feeds from torrent indexers to download clients and *arr applications. It listens to real‑time announcements, filters releases based on user‑defined rules, and pushes matching torrents to qBittorrent, Deluge, Transmission, rTorrent, or the Sonarr/Radarr/Lidarr ecosystem. The platform supports Docker, native binaries for Linux, macOS, Windows, and FreeBSD, and integrates with popular notification services like Discord, Telegram, and Pushover. autobrr aims to streamline torrent acquisition, reduce latency between announcement and download, and provide a flexible API for custom extensions.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles autobrr the way a machine reads it — 31 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — autobrr scores 35.8/100 (thin), with a separate agent-readiness read of 41/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Why this profile is thin
The autobrr REST API reference page provides human‑readable HTML but no published OpenAPI, AsyncAPI, GraphQL, or other machine‑readable contract.
The documentation is public — a person can read it, but a machine cannot. This one is autobrr's to change: publishing an OpenAPI (or AsyncAPI for events) at a stable URL would make the same surface consumable by a crawler, a linter, and an AI agent.
What we probed
https://autobrr.com/api→ HTTP 200
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-10-31 · rubric v0.25.0
Put this on your own site. The badge is drawn live from autobrr's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/autobrr/"
title="autobrr on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/autobrr.svg"
alt="autobrr Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/autobrr/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/autobrr/"
title="autobrr on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/autobrr/card.svg"
alt="autobrr Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile autobrr
Each block below is one kind of artifact we hold for autobrr. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 25
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
autobrr API Keys API
API key management
autobrr ARR Integrations API
Sonarr/Radarr instance management for external ID lookups
autobrr Authentication API
User authentication and session management
autobrr Backups API
The Backups API from autobrr — 5 operation(s) for backups.
autobrr Categories API
Category management
autobrr Client API Keys API
Client API key management for external applications
autobrr Client Settings API
The Client Settings API from autobrr — 1 operation(s) for client settings.
autobrr Cross Seed API
Cross-seeding operations for finding and adding duplicate torrents
autobrr Dir Scan API
Directory scanner operations for data-based matching and injection
autobrr Disc Scans API
BDInfo scans of Blu-ray Discs (BDMV folders and .iso files) in torrents
autobrr External Programs API
Manage and execute external applications
autobrr Instances API
qBittorrent instance management
autobrr Licenses API
The Licenses API from autobrr — 6 operation(s) for licenses.
autobrr Notifications API
Notification-related endpoints for targets and events
autobrr Orphan Scan API
Orphan file scanning and cleanup (files on disk not associated with any torrent)
autobrr Proxy API
qBittorrent-compatible proxy endpoints authenticated by client API key
autobrr RSS API
RSS feed and auto-download rule management
autobrr System API
The System API from autobrr — 12 operation(s) for system.
autobrr Tags API
Tag management
autobrr Themes API
Sideloaded custom theme listing (premium)
autobrr Torrent Details API
Individual torrent information
autobrr Torrents API
Torrent operations
autobrr Torznab API
The Torznab API from autobrr — 4 operation(s) for torznab.
autobrr Tracker Icons API
The Tracker Icons API from autobrr — 1 operation(s) for tracker icons.
autobrr Trackers API
The Trackers API from autobrr — 1 operation(s) for trackers.
Scroll within the panel for all 25 ·
Event Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Autobrr Webhooks
ASYNCAPISemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Autobrr Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
autobrr API Rules
SPECTRALSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for autobrr — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Company 1
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/autobrr · machine-readable index on apis.io
This is an independent, third-party profile of autobrr, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.