How do agencies automate video editing?

By wiring the recurring deliverables to the API. A webhook announces when a client's session is ready; your tooling posts the standing brief to /v1/cuts; a second webhook announces the plan; a producer reads it; renders are requested and a third webhook announces each finished file. Agents can drive the same loop through the MCP server. Send an idempotency-key on any request that creates something, so retries are safe.

Can each client's footage stay separate?

Yes, by running one account per client - and it is worth knowing why: within a single account, access is account-wide today, with roles governing settings, billing and membership rather than who sees which library. The account boundary is therefore where separation is absolute: library, API keys, webhooks, brand kits and billing all live inside it, and a brief can only draw on sessions in the account it runs in.

Can deliverables carry each client's branding?

Each client account holds that client's brand kits: caption typeface and colours, logo, end cards per aspect ratio. Every render that names a kit ships with captions styled to it, the logo watermarked top-right and the end card appended as a two-second still - the same treatment on week one and week fifty.

Which plan fits an agency?

Studio, at £249 a month for 1,500 source minutes - twenty-five hours of single-camera footage, or two cameras each metered. Where clients run in their own accounts, each account carries the plan its volume needs, so a heavy retainer can sit on Studio while a lighter one sits on Pro. Minutes are counted once, at ingest; briefs, plans, revisions and re-renders use none.

For agencies

Deliver the month,
for every client.

Retainers are won on judgement and kept on delivery. Video editing automation for agencies, as Anjin Media builds it, turns the deliverables that repeat into written briefs your team runs - or wires to the API - while every client stays inside an account of their own: separate library, separate keys, separate billing.

Plans are read before anything renders, so the work that carries your name still passes through your judgement.

Create an edit See pricing

One video or an entire archive.

The problem

The retainer's arithmetic.

Beneath every showpiece film sits the drumbeat: weekly recaps, podcast cutdowns, event verticals, the case-study edit each new logo needs - work that is won as recurring revenue and then produced, month after month, out of senior hours. Margin erodes exactly where the revenue was supposed to be predictable.

Hiring resets the ceiling without changing the shape: the tenth client still costs what the third did. What scales is a system, not a headcount - briefs that repeat, checkpoints that protect quality, and machinery that carries files, formats and captions without a person attached.

The single-deliverable version of this workflow - one long recording into short, briefed cutdowns - is on the long-to-short page →

Repeatable delivery

The deliverable becomes a brief you keep.

A recurring deliverable has a stable shape: the client's episode recap is always a minute, always widescreen plus vertical, always ends on the call to action. Written down once as a brief, that shape becomes the week's work - point it at the new session, read the plan, render. The craft moved into the brief; the hours moved out of the edit.

Throughput follows because review is cheap where it matters. A plan lists its segments with transcript text and source timecodes, so a producer checks the argument in a minute - and striking or reordering segments applies instantly, at no cost. Plain-language revisions cost nothing either, and neither does rendering; only the footage you ingest counts.

Every client's history compounds. Sessions stay indexed in that client's account, so February's case-study brief can draw on January's recording - up to four named sessions per brief - without anyone re-uploading or re-watching a frame.

THE STANDING BRIEF · CLIENT BAUGUST

“Cut this month’s client webinar to the strongest sixty seconds; open on the sharpest claim; end on the booking call to action.”

target_duration_s 60aspects ["16:9", "9:16"]

WK 1EPISODE RECAP · 1:00 · 16:9 + 9:16DELIVERED
WK 2EPISODE RECAP · 1:00 · 16:9 + 9:16DELIVERED
WK 3EPISODE RECAP · 1:00 · 16:9 + 9:16IN REVIEW
WK 4EPISODE RECAP · 1:00 · 16:9 + 9:16BOOKED

SAME BRIEF SHAPE · NEW SESSION EACH WEEK

API automation

A pipeline with one manual step.

The full delivery workflow is callable: source groups, cuts, plans, renders and brand kits over REST, with scoped Bearer keys per account and webhooks announcing the moments worth reacting to - a session turning ready, a plan arriving, a render landing. The MCP server exposes the same operations to agents, tool by tool.

The step left manual is the one your name depends on. Automation carries a deliverable to the plan; a producer reads it before renders are requested, because rendering is the step that spends. For flows you trust end to end, auto-render on the first plan is one flag.

Deliverables leave the pipeline finished: each render arrives with SRT captions, an EDL in JSON and a QC report - the file for the channel and the paper trail for the client, in the same delivery.

ONE DELIVERABLE, AUTOMATEDREST + WEBHOOKS

source.readywebhook - the session landed
POST /v1/cutsthe standing brief, idempotency-key set
cut.plannedwebhook - the plan is readable
producer reads the planthe checkpoint, before spend
POST /v1/cuts/:id/renders16:9 + 9:16 off one plan
render.completedwebhook - into client delivery

RENDERING USES NO MINUTES · THE CHECKPOINT COMES FIRST

Where agencies start

Studio, and the boundary that matters.

Studio

£249 / month

1,500 source minutes a month (25 hours of single-camera footage)
Two cameras, each metered

ANNUAL · £2,700 A YEAR

The recommended shape is one account per client, each on the plan its volume needs. Said plainly: the platform has no sub-accounts or client workspaces, and inside one account access is account-wide - so the account boundary is the separation, and it is a hard one. Keys, webhooks, brand kits, library and bill all sit within it. Offboarding a client means handing over or deleting that account's library - deletion is self-serve and purges storage; closing the account itself goes through support.

The full request surface is on the API page, the agent tooling on the MCP page, and integration details in the docs. Plans in full are on pricing.

The objections

What a client will ask you.

Our clients will ask what the AI did to their footage.: Answer with the paper trail. Every edit began as a written brief; its plan listed each segment with source timecodes before rendering; the delivered file carries an EDL in JSON naming exactly which session and which seconds every segment came from. No generative footage enters an edit: every frame is selected from the client's own recording. Few production workflows can show a client that much of their own working.
What happens when a client leaves - do we hold their footage hostage to our tooling?: No. Their material lives in their own account, and deletion is real and self-serve: removing a source group purges its media from storage. Offboarding is handing over or deleting the client's library that way; closing the account itself is a support request, not a self-serve toggle. Renders and their sidecars were already delivered as files. The account-per-client pattern costs a little admin at setup and pays for it at every offboarding.

Questions

How do agencies automate video editing?: By wiring the recurring deliverables to the API. A webhook announces when a client's session is ready; your tooling posts the standing brief to /v1/cuts; a second webhook announces the plan; a producer reads it; renders are requested and a third webhook announces each finished file. Agents can drive the same loop through the MCP server. Send an idempotency-key on any request that creates something, so retries are safe.
Can each client's footage stay separate?: Yes, by running one account per client - and it is worth knowing why: within a single account, access is account-wide today, with roles governing settings, billing and membership rather than who sees which library. The account boundary is therefore where separation is absolute: library, API keys, webhooks, brand kits and billing all live inside it, and a brief can only draw on sessions in the account it runs in.
Can deliverables carry each client's branding?: Each client account holds that client's brand kits: caption typeface and colours, logo, end cards per aspect ratio. Every render that names a kit ships with captions styled to it, the logo watermarked top-right and the end card appended as a two-second still - the same treatment on week one and week fifty.
Which plan fits an agency?: Studio, at £249 a month for 1,500 source minutes - twenty-five hours of single-camera footage, or two cameras each metered. Where clients run in their own accounts, each account carries the plan its volume needs, so a heavy retainer can sit on Studio while a lighter one sits on Pro. Minutes are counted once, at ingest; briefs, plans, revisions and re-renders use none.

Put the drumbeat on rails.

Start with one client and one recurring deliverable. When the third week takes minutes, wire it to the API.