Venice keysVeniceLearn · GuidesOpen Venice ↗
Guide · Video

Build and edit long-form AI videos with the Venice Video Harness

This guide shows how to produce a roughly 60 second cinematic trailer using Venice's API inside an IDE, generating consistent characters and shots automatically and then fine-tuning them with natural language or the Venice Studio interface.

Watch the full walkthrough
What you'll learn
  • Why an API-driven workspace beats a web interface for longer videos
  • How to clone the Venice Video Harness, add your API key, and start a project
  • How character consistency, reference-to-video models, and a QA agent keep shots on-model
  • When to drop into Venice Studio for Seedance 2.0 shots, music, and final editing
  • How to assemble and sync a finished trailer in the Venice Movie Editor

Why move from a web interface to an API workspace

Venice currently serves close to 60 video models, covering text to video, image to video, and video to video, all private and uncensored. A web interface is comfortable and useful for fine-tuning, but when you are juggling that many models across a longer project, the API gets work done faster with less manual back-and-forth.

Two GitHub repos support this workflow. The first is a skill for model routing: it generates reference images, edits images to fix faces, and routes each step to the right model. The second, the Venice Video Harness, is a full workspace you run inside an IDE like Cursor or Visual Studio Code using Claude Code or OpenCode. The harness is built to one-shot a longer video, then let you fix it up in plain language. This guide focuses on the harness because your agent drives most of the process for you.

Setup: API key, DIEM staking, and cloning the repo

You need a Venice API key and credits. Venice is the private API option and exposes over 160 models across text, image, audio, and video, all of which this project touches, so you avoid stitching together scattered providers.

For an ongoing hobby like video work, look at the DIEM token. Stake one DIEM and you receive a dollar of Venice API credits every day; stake 10 and you get $10 daily that refreshes, paid for once. To start the project, copy the GitHub repo URL (or download the zip), open your IDE, choose clone repo, and paste the URL. Open the fresh workspace and paste your Venice API key where indicated. Look around and you will find the behavioral context file that tells the agent what the harness does, plus the sub agents and skills it uses. Because the repo is updated over time, you can run a git pull to get fixes or send your own pull request.

Planning mode and the character reference system

Begin by telling the IDE what you want, for example a sci-fi cinematic trailer about 60 seconds long. Using Opus 4.6 in Cursor, switch into plan mode. The agent asks about style, story concept, and cast size, and you can answer or just say "develop a concept for me, surprise me." It then builds reference files for each character and a set of reusable scenes such as a wide shot of a monolith or the chamber of the Oracle, which it later drops characters into.

Consistency comes from the character consistency skill. It generates four reference angles per character: front, three-quarter, profile, and full body. It also picks the model, currently a Kling reference-to-video model, so the frontal image and reference images can be passed as parameters in the API call. These reference-to-video (R2V) models are how you reach the highest-quality, on-model output. The harness also ships commands for producing a series, a trailer, a single video, an aesthetic exploration, or a character, so you choose how much to hand off versus do yourself.

The shot pipeline and the QA agent

The harness generates images and turns them into shots one at a time. Each shot gets a JSON file recording the model and the prompt, alongside the reference image used. You can open these to see exactly what the API was sent.

Quality assurance runs automatically. The storyboard QA agent analyzes generated panels for character consistency, checks that prompts are detailed enough, regenerates anything that does not match the reference, and archives the bad files. In the example, a generation drifted off-model and a logo came out as plain "VVV" instead of the reference image, so the system flagged and corrected it before settling on the final shot to animate. This extra checking is why the harness spends more tokens and credits, but it means far less input from you.

Natural-language edits and when to use Venice Studio

After the shots are generated and fixed, the harness stitches a final version you can watch, and you refine it conversationally. You can say things like:

Cut the first two seconds of shot three and the last half second.
Add a cross dissolve between shots one and two.

The agent rebuilds the final video from those instructions. Some shots are still better handled by hand, so it helps to open the Venice Studio interface. There you can reload a draft to restore its prompt, inspect the attached elements (such as the Oracle and the protagonist with their reference images) and the scene, and regenerate manually. The harness knows the API docs and models cold, but sometimes you are the creative director and want to craft the prompt yourself.

Seedance 2.0 and reference-to-video shots in the UI

At the time of recording, Seedance 2.0 is only available through the Venice UI, not the API, and it produces some of the most cinematic, detailed shots, with multi-shot cuts in a single generation. Its R2V approach differs from Kling: instead of structured elements, you simply attach reference images for your characters and scenes and write a prompt that tags them.

A working prompt pattern tags each reference image by number:

Image one: wide establishing shot showing the chamber.
Image two: walks into the image one chamber and looks around desperately,
wide shot, before a sudden explosion. Cut to a medium shot of image two
falling down, looking anxious, and beginning to run away.

You can run AI prompt enhancement (the same step the harness performs) and re-tag images if the model loses track. Expect occasional content-filter rejections on certain reference images; swap in a different reference and continue. The UI also makes it easy to copy the last frame and keep generating, which is harder inside the IDE.

Series files, scripts, and music with timing cues

The harness creates a series file at the start holding everything it needs: aesthetic, setting, genre, characters and their looks, optional voice descriptions, episode number and status, aspect ratio, and default models. It also writes a full episode script listing every shot, its type, model, and description, which you can use as a reference for adding your own sound or effects tracks. Each shot keeps its own JSON prompt that you can paste straight into Venice Studio.

For music, the harness generates a track and you can ask it which prompts it used. To make music in the UI, click the plus in the chat, choose generate audio, and pick a model; ElevenLabs handles instrumental scores, sound effects, and voice well. Set the length and write a prompt, and you can steer timing directly:

First 10 seconds soft and mysterious. Next 20 seconds intense.
Following 10 seconds calms down. Final crescendo during the final 15 seconds.

As the project grows, watch the context window. Opus 4.6 offers a million tokens, but quality degrades as it fills; the agent may forget to use a skill, so keep an eye on it. Files accumulate too: the harness keeps a base shot name like shot_007 and appends V1, V2, or pre-render versions so you can trace the pipeline and clean up at the end.

Final assembly and trailer review

When the stitched draft has rhythm problems, such as shots running too long, take it into proper editing software. You can use the Venice Movie Editor: drag shots onto the timeline, cut and arrange them, and mix in clips you generated in the UI. The Cursor-generated audio folder holds the music track, regenerated per version, ready to drop in.

The finished trailer shows shots synced to the score. The music was generated in one pass, not hand-edited; the shots were simply cut to match it, which the Movie Editor makes approachable if you are new to nonlinear editing. Moving in and out between the IDE and Venice Studio gives you both speed and fine control: let natural language and reference shots handle consistency, and step into the UI when you want a specific shot exactly right.

Key takeaways

Adapted from the @askvenice video on YouTube. Models and prices change fast; verify current details in Venice before production use.