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?

Organise work by client brand within the Agency account when your team can share access. Access is account-wide; brand kits do not create private client libraries. If a client needs an isolated library, keys and membership, use a separate account with its own paid plan or explicitly quoted licence and allowance. Usage is not pooled across those accounts.

Can deliverables carry each client's branding?

Your team can use a brand kit for each client for each client brand in the account: 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.

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 - with one team account sharing its contracted usage across client brands.

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. AI and plain-language revisions are included; each rendered aspect uses export minutes.

Every client's history compounds. Sessions stay indexed in the account your team uses, 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

REVIEW THE PLAN BEFORE USING EXPORT MINUTES

Where agencies start

Agency, with clear usage allowances.

Agency

£999/month + VAT

£1,198.80 incl. 20% UK VAT

2,400 source minutes a month
600 export minutes a month
400 GB active storage
AI included
Multiple cameras included
Unlimited editors
Unlimited brands

Studio and Agency include unlimited editors and brands within one account. An Agency team works in one account with one contracted set of source, export and storage allowances across its client brands. Team members and brands share those allowances. Adding brands or accounts does not add usage; separate accounts need their own paid plan or an explicit licence and allowance in an Enterprise quote.

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?: Deliver the client’s renders and sidecars as files, then remove their source groups if your agreement requires deletion; that operation purges their media from storage. Check the selected groups carefully when the account serves several clients. A client needing independent control can use a separately paid account; sharing an Agency brand kit does not create an isolated client workspace.

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?: Organise work by client brand within the Agency account when your team can share access. Access is account-wide; brand kits do not create private client libraries. If a client needs an isolated library, keys and membership, use a separate account with its own paid plan or explicitly quoted licence and allowance. Usage is not pooled across those accounts.
Can deliverables carry each client's branding?: Your team can use a brand kit for each client for each client brand in the account: 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?: Agency is £999 + VAT (£1,198.80 incl. 20% UK VAT) a month, with 2,400 source minutes, 600 export minutes, 400 GB of active storage and AI included. Studio and Agency include unlimited editors and brands within one account. An Agency team works in one account with one contracted set of source, export and storage allowances across its client brands. Team members and brands share those allowances. Adding brands or accounts does not add usage; separate accounts need their own paid plan or an explicit licence and allowance in an Enterprise quote.

Put the drumbeat on rails.

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