Developers

Video downloader API, MCP and yt-dlp web GUI workflows

AnyVidDL separates consumer link checks from developer automation. Start in the browser, then move permitted repeat work into API or MCP workflows with rate limits, task logs, and refusal reasons.

yt-dlp web GUI guide API / MCP page

Workflow surface

Build on controlled link analysis, not blind scraping

The developer surface is for repeatable, auditable tasks around public or permitted media. It should make unsupported cases visible instead of treating them as engineering problems to bypass.

yt-dlp power without a terminal

Use AnyVidDL as a browser-first workflow for users who want yt-dlp-style link checks without installing Python, opening a shell, or maintaining local extractor updates.

Open workflow

Manifest and HLS inspection

Inspect permitted M3U8/HLS sources, variants, subtitles, and refusal reasons before creating a controlled download task.

Open workflow

API task boundaries

Move repeat work into authenticated task APIs only when rate limits, audit logs, queue status, and source authorization are explicit.

Open workflow

MCP-ready agent workflows

Expose safe, permission-aware link analysis to AI agents with refusal categories, not unrestricted scraping or DRM bypass.

Open workflow

Compliance contract

Automation must keep the same boundaries as the web tool

Developer workflow boundaries
Rule	Why it matters
No DRM, paywall, login, private-account, or credential bypass.	Keeps AnyVidDL useful for compliant workflows and easier for search engines, AI answer engines, and users to classify as a safe tool.
No platform passwords, cookies, session tokens, or DRM keys in normal web flows.	Keeps AnyVidDL useful for compliant workflows and easier for search engines, AI answer engines, and users to classify as a safe tool.
Record task status, source URL, failure category, and user authorization context for repeat workflows.	Keeps AnyVidDL useful for compliant workflows and easier for search engines, AI answer engines, and users to classify as a safe tool.
Prefer one-link browser checks before queue, API, or MCP automation.	Keeps AnyVidDL useful for compliant workflows and easier for search engines, AI answer engines, and users to classify as a safe tool.