Developers

Jumper runs locally and handles the heavy work: analyzing footage, visual and speech search, face recognition, thumbnails, and exports. You build the workflow layer: a review UI, a batch tool, a facility pipeline, or an NLE plugin tailored to how you actually edit. Everything stays on your machine. Your app talks to the Jumper backend over a local API at http://localhost:6699/api/v1.

​

What Jumper handles vs what you build

Jumper handles:

• Visual, transcript, and image search across analyzed media
• Speech transcription and face clustering
• Thumbnails, metadata, and clip exports
• Watch folders and analysis data management

You build:

• The interface or automation that fits your workflow
• How results are reviewed, saved, renamed, or handed off
• Integrations with other tools you already use

Your app does not need to solve video AI, indexing, or media analysis. It calls Jumper and focuses on the part only you know: your bins, naming conventions, review rituals, and handoffs.

​

How it fits together

​

Two ways to extend Jumper

Use the Public API when you want a standalone app, script, or integration that runs the same way every time. Use MCP when you want a conversational agent to figure out the steps on the fly.

​

Who this is for

• Editors with a niche workflow that the main Jumper UI does not cover
• Post supervisors and facility teams automating recurring steps across a shop
• Developers building tools on top of local media analysis

You do not need to be a programmer to get started with the Public API. If you can describe what you want clearly, a coding agent (Cursor, Codex, Claude Code, or similar) can build a first version from the API reference and OpenAPI spec. For a walkthrough of building and iterating on a custom app, see the Jumper blog:

• Vibe Coding for Video Editors 101
• Vibe-Coding Your Own Video Editing Tools

​

What people build

Common starting points:

• A custom search and review UI (timeline, deck, keyboard-driven selects)
• A batch export or rename tool for dailies or stringouts
• A facility script that searches analyzed media and writes results to shared storage
• A small local web app that combines Jumper results with another tool you already use

Start small. Prove the connection works, then add features one at a time.

​

Before you begin

Have these ready:

• Your Jumper Pro license key: find it in the Settings tab
• The path to your analysis folder: configured in Settings
• Analyzed media: search only works on footage Jumper has already processed. See Processing.

​

Get started

​

Share what you build

Built something useful, chaotic, or both? We would like to see it.