AI video agent vs a single-model video generator: what you call
A single-model generator returns one clip from a prompt. An agent plans shots, calls tools and assembles a video. How the Sume calls differ.

A single-model generator turns a prompt into one clip, so you do the planning, cutting and audio yourself. A video agent takes a brief and decides which generation tools to call, then assembles the result. Runway's announcement describes Agent as going from idea to a finished, ready-to-publish video in a single conversation; on Sume the same split is generate_video for one model job and an Agent Completions or Format run for the assembled video.
The two shapes
| Question | Single-model call | Agent or Format run |
|---|---|---|
| Input | A prompt for one clip | A brief, plus images or product data |
| Who plans | You | The agent |
| Output | One clip | A finished piece, with media files and a result |
| Sume entry | generate_video on the hosted MCP, or the video routes | POST /v1/formats/{handle}/{slug}/runs or /v1/agent/completions |
| Spend control | dry_run and max_spend_usd on the tool | generation_spend_cap_usd on the run |
| Typical wait | Job time of one model | Long-form host video typically takes 15 to 30 minutes |
When the single call is right
- You already have a storyboard and want a model to render each shot.
- You are comparing models on one prompt.
- You need the cheapest possible preview of a single shot.
When the agent is right
When the work is a chain of decisions, such as a script, takes, B-roll, voiceover, captions and a cut, hand the chain to a Format run. It stays inside a cap you set, and the run is unattended, so write the quality bar into the instruction.
Start with a capped run
The body below is a complete run request. Replace the instruction with your brief and keep the cap low while you learn what a run costs.
{
"instruction": "Make a 30-second product video for a trail mug.",
"generation_spend_cap_usd": 20
}Sources
Related posts
More in Agents
- @-mention an agent on a video asset: Runway vs Sume
Runway Enterprise lets you @-mention its Agent in asset comments. Sume Agents take work via the Agent Completions API; media jobs report by webhook.
- Re-render Sora prompts from an agent: jobs_wait takes 20 ids
An agent re-rendering saved Sora prompts should wait on up to 20 Sume job ids per call, read results in one batch, and not resubmit after a wait slice expires.
- Claude Code 2.1.289 agent.spawn: teammates share one Sume queue
Claude Code 2.1.289 adds agent.spawn for teammates. Teammates sharing a Sume workspace share its concurrency limit and queue, so plan the width of the fan-out.
- Claude Desktop catch-up run after wake: idempotency key for Sume
Desktop runs one catch-up task after sleep, maybe hours late. Use a date-based idempotency_key, dry_run and max_spend_usd so Sume bills once.
Written by Sume