Medusa (TV) website screenshot

Medusa (TV)

Medusa (TV) is an open-source automated video library manager designed for TV show enthusiasts. It continuously monitors your favorite series for new episodes, automatically downloading, organizing, and renaming them according to your preferences. Built with Python, it integrates with popular indexers, download clients, and media servers, providing a seamless experience for keeping your collection up to date without manual effort.

Medusa (TV) publishes 1 API contract indexed on the APIs.io network. Tagged areas include Company, TV, Media, Automation, and Open Source.

The Medusa (TV) catalog on APIs.io includes 1 Spectral governance ruleset.

Medusa (TV)’s developer surface includes documentation, support, and 10 more developer resources.

13.9/100 emerging ▬ flat Agent 3/100 human only Heartbeat 100/100 alive Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →
AccessOpen
1 published contract
CompanyTVMediaAutomationOpen SourcePython

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-11-13 · rubric v0.28.0
Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.
The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site. Kin Score badge preview for Medusa (TV) It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/pymedusa/"><img src="https://apis.io/badge/pymedusa/card.svg" alt="Medusa (TV) on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
  • Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document Ask about this →
  • MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship Ask about this →
  • Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author Ask about this →
  • Machine-Readable Auth +10 pts — a served openid-configuration/oauth-authorization-server carrying `issuer` (served), else the securitySchemes class in the provider OpenAPIs — bound (mutualTLS, DPoP, Signature) > negotiable (oauth2 authorizationCode/clientCredentials, openIdConnect) > bearer (http bearer, apiKey) Ask about this →
  • Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented) Ask about this →
  • A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0 Ask about this →
11 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.
Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →
Ask about:
Pymedusa · a person reads this and replies by email.
or email info@apis.io
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/pymedusa/apis.yml: open an issue on github.com/api-evangelist/pymedusa to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

MinIO Browser

MinIO Browser UI hosted at pymedusa.com.

Rate Limits 1

Documented rate limits and quota policies.

Medusa (TV) Rate Limits

0 limits

RATE LIMITS

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs. Counts are the severity each rule declares, not results of running them.

Medusa (TV) API Rules

9 rules · 7 error-severity 1 warn-severity 1 info-severity

SPECTRAL

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Medusa (TV) Authentication

0 schemes

SECURITY

Medusa (TV) Domain Security

TLSv1.3 · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Medusa (TV) Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Resources

Documentation 1

Reference material describing how the API behaves

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 1

Authentication, authorization, and security posture

Operate 1

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

Source (apis.yml)

apis.yml Raw ↑
aid: pymedusa
name: Medusa (TV)
description: Medusa (TV) is an open-source automated video library manager designed for TV show enthusiasts. It continuously
  monitors your favorite series for new episodes, automatically downloading, organizing, and renaming them according to your
  preferences. Built with Python, it integrates with popular indexers, download clients, and media servers, providing a seamless
  experience for keeping your collection up to date without manual effort.
url: https://artifacts.apis.io/pymedusa/apis.yml
x-type: company
x-source: harvest:new-submission
x-tier: profiled
x-tier-reason: enrichment pass 2026-10-28 (modular-v1; was harvest)
accessModel:
  pricing: unknown
  onboarding: open
  trial: false
  try_now: false
  public: true
  gated: none
  gated_source:
  - onboarding
  label: Open access
  confidence: low
  probe_state: unreadable
  source:
  - authentication
  - security
  generated: '2026-11-13'
  method: derived
specificationVersion: '0.20'
created: '2026-10-28'
modified: '2026-10-28'
tags:
- Company
- TV
- Media
- Automation
- Open Source
- Python
tags_raw:
- Company
- TV
- Media
- Automation
- OpenSource
- Python
image: https://avatars.githubusercontent.com/u/16712498?v=4
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Spectral
  url: rules/pymedusa-rules.yml
- type: DataModel
  url: data-model/pymedusa-data-model.yml
- type: Conventions
  url: conventions/pymedusa-conventions.yml
- type: ErrorCatalog
  url: errors/pymedusa-problem-types.yml
- type: Conformance
  url: conformance/pymedusa-conformance.yml
- type: Hosts
  url: hosts/pymedusa-hosts.yml
- type: Vendors
  url: vendors/pymedusa-vendors.yml
- type: Website
  url: https://pymedusa.com/
- type: DomainSecurity
  url: security/pymedusa-domain-security.yml
- type: GitHubOrganization
  url: https://github.com/pymedusa
- type: Documentation
  url: https://github.com/pymedusa/Medusa#readme
- type: Support
  url: https://github.com/pymedusa/Medusa/issues
apis:
- name: MinIO Browser
  description: MinIO Browser UI hosted at pymedusa.com.
  humanURL: https://pymedusa.com/minio/
  aid: pymedusa:minio-browser
x-coverage:
  state: unreadable
  reason: no-machine-readable-spec
  detail: The provider's site hosts a MinIO Browser UI but does not publish any machine‑readable API specification.
  evidence:
  - url: https://pymedusa.com/minio/
    status: 200
  checked: '2026-10-28'
x-submission-probe: 307 https://pymedusa.com/minio/, 2026-10-26
x-enrichment:
  date: '2026-10-28'
  status: enriched
  artifacts_added: 20
  pass: modular-v1
  engine: identity=oss,contract=oss,surfaces=oss,docs=oss,regulatory=oss

Medusa (TV) API — frequently asked questions

Does Medusa (TV) have an API?

Yes. APIs.io lists 1 API from Medusa (TV), including MinIO Browser.

How do I authenticate with the Medusa (TV) API?

Medusa (TV) documents its authentication (0 schemes). The details are profiled on APIs.io as Medusa (TV) Authentication.

Is the Medusa (TV) API ready for AI agents?

Medusa (TV) has a Kin Score of 13.9 out of 100 (emerging) and an Agent Readiness score of 3.2 (human-only), scored by API Evangelist on 2026-11-13.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/pymedusa"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/pymedusa/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/pymedusa/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.