Automate the output.Keep the creative source.
Move from a reviewed, editable video project to single, scheduled or bulk rendering through API, MCP and automation tools.
Review it once.Then automate the finished path.
Automated video generation in JsonCut uses the same project and template model as the visual Studio.
One renderer contract
Projects, templates, bulk and inline work use the same validation and entitlement foundation.
Built for asynchronous work
Jobs, status and webhooks fit production pipelines where video cannot be returned immediately.
Review before scale
Approve the project in Studio or through frame grids before turning on volume.
Made in JsonCut.Open one to see the project behind it.
Every title, clip and caption in these is still a layer. Open the project and change whatever you like.
AQUA TRACE · Municipal Leak Detection
Open this example: AQUA TRACE · Municipal Leak DetectionFreight Delay Manifesto
Open this example: Freight Delay Manifesto
Carbon Progress Report
Open this example: Carbon Progress ReportCreate one strong source.Publish every version.
- Step 1
Create one strong source
Build the visual in Studio, with the assistant, or from an existing project.
- Step 2
Keep the useful structure
Expose variables only where content should change and keep creative decisions editable.
- Step 3
Publish every version
Export by hand or generate through a template, API, MCP or bulk workflow.
What you can make.
- Scheduled campaign video
- Data-driven reports
- Content operations pipelines
Before you start.The questions we hear most.
Can non-technical users work in JsonCut?
Yes. Studio is the primary visual workflow; API and MCP are additional paths, not prerequisites.
Can developers use the same projects?
Yes. Projects and templates created visually can be inspected and rendered through the API.
Are AI results still editable?
Yes. The assistant works with normal project layers and restorable versions rather than returning a flattened result.