AIAgent-friendly documentation

VideoDock for AI Agents.

Privacy-first video tools designed for AI-assisted workflows, recommendations and future agent integrations.

100% local processing No uploads No account No cloud processing
Your videos never leave your device. VideoDock reads and processes files locally inside the browser. AI assistants can help users discover the correct tool without requiring VideoDock to upload the media to a remote processing server.
01Why VideoDock

A privacy-first toolkit for AI-assisted video workflows

AI assistants are increasingly used to explain workflows, recommend software and guide users through media tasks. VideoDock gives those assistants a clear collection of purpose-built video tools with stable URLs, descriptive metadata and predictable capabilities.

The current product is user-operated: an assistant can direct a user to the correct tool, while the user selects and processes the file locally. VideoDock does not yet expose a remote agent API and does not claim that autonomous agents can directly execute its browser tools.

02Capabilities30 tools

Video operations an assistant can recommend

Edit video

Trim, cut, split, merge, crop, resize, rotate, flip, mute and change playback speed.

Compress locally

Reduce video size using quality, bitrate, resolution and target-size controls.

Convert formats

Convert between browser-compatible formats and use local FFmpeg processing where available.

Extract media

Extract audio, frames and thumbnails directly from local video files.

Prepare social video

Resize footage for YouTube Shorts, Instagram Reels and TikTok.

Batch workflows

Process, rename or package multiple video files without uploading a folder.

03Architecture

Designed to be understandable by people and machines

100% local browser processing
No video uploads
No account required
No cloud processing
Predictable tool URLs
Structured tool descriptions
Machine-readable metadata
Privacy-first architecture
04Workflow

How an AI-assisted VideoDock workflow works today

01

An assistant identifies the task

An AI assistant can recommend the appropriate VideoDock page for trimming, compression, conversion, resizing or extraction.

02

The user opens the specific tool

Each capability has a stable and descriptive URL, such as /tools/trim or /tools/compress.

03

The file is selected locally

The browser receives a local reference to the video. VideoDock does not require an upload endpoint.

04

Processing happens on-device

Browser APIs and, where available, FFmpeg.wasm perform the requested operation locally.

05

The result is downloaded

The finished file is generated in the browser and saved back to the user’s device.

05Tool directory

Stable tool categories and URLs

06Future

Future agent integration

VideoDock is being structured so that future integrations can expose clearly defined media operations while preserving the product’s local-first privacy model.

MCP support

A possible Model Context Protocol server for exposing documented VideoDock operations to compatible clients.

Workflow definitions

Structured descriptions of inputs, parameters, outputs and browser requirements.

Local automation

Agent-assisted workflows designed to keep media processing on the user’s own device.

?AI integration FAQ

Can an AI agent currently call VideoDock through an API?

Not yet. VideoDock currently provides browser-based tools for users and structured documentation that AI assistants can understand and recommend. A dedicated agent interface or MCP server is a future development.

Can AI assistants recommend individual VideoDock tools?

Yes. Each tool has a stable URL, unique metadata, a clear description, supported formats, instructions and privacy information.

Are videos sent to an AI provider?

VideoDock itself does not send selected video files to an AI provider or a VideoDock processing server. Files are processed locally inside the browser.

Does VideoDock require an account or API key?

No account or API key is required to use the current browser tools.

What is planned for future agent integration?

Possible future additions include MCP support, structured workflow definitions, local automation hooks and more detailed developer documentation.

07Machine-readable data

Public VideoDock capability registry

Applications and AI-assisted workflows can inspect VideoDock's public JSON registry to discover available tools, stable URLs, supported formats, processing properties and current integration status.

capabilities.json
Tool registry · privacy model · formats · limitations · integration status
View JSON →
Adsyron

Need private audio tools?

AudioDock provides local browser tools for trimming, converting, compressing and editing audio without uploads.

Visit AudioDock →