Product launch
“Create a cinematic product reveal with a confident hook, three benefits, and a direct CTA.”
Give Claude, Codex, Cursor, or your own agent a real video engine for composing, rendering, previewing, and delivering production-ready videos.
Create a cinematic 9:16 launch video for our new AI workspace. Use three scenes, captions, and a confident CTA.
These are the kinds of outputs your agent can create when it has composition, rendering, and review tools in the same loop.
“Create a cinematic product reveal with a confident hook, three benefits, and a direct CTA.”
“Turn these product benefits into a clean explainer with kinetic type and a soft blue palette.”
“Build a fast social story with a bold first frame, captions, and a loopable ending.”
“Generate localized product videos for every row in this campaign spreadsheet.”
MCP tools handle actions. Skills add context. VideoJSON keeps every render deterministic.
Turn an idea into a hook, story, proof, and CTA before a frame is rendered.
intent → BRIEF.mdBuild scenes, layers, transitions, captions, and effects through a typed contract.
VideoJSON → scenes[]Queue one video or thousands of variants with status, credits, and signed delivery URLs.
job → mp4 + webhookPreview, capture, measure, and analyze layouts so agents can debug their own output.
render → inspect → fixYour agent does not need to understand a dozen disconnected APIs. It speaks one composition language from the first idea to the final MP4.
Your agent turns a simple brief into a structured video plan.
Create a 15s product launch videoVideoJSON gives every scene, layer, effect, and timing a contract.
scenes: [hook, reveal, cta]The same composition moves through the browser, server, or edge renderer.
job_01HQ... · 68%Poll the job, fetch a signed URL, and deliver the final MP4 to your workflow.
https://cdn.../video.mp4Create a 15-second vertical product launch video.
Use the product-promo template.
Add captions and a confident CTA.{
"jobId": "render_01HQ7K",
"status": "queued",
"format": "1080x1920",
"webhook": "ready"
}The agent loop stays reviewable when output size and render cost are explicit before a job starts.
The baseline is 1080p30 rendered video. Cost scales with duration, resolution, and frame rate.
Preview the render-cost estimate before an agent spends credits.Use the same contract for a single preview or a queue of variants.
Use the interface that matches your product: MCP for agents, SDK and REST for code, CLI for CI, and workflow nodes for automation.
Same rendering engine. Different entry point.
MCP tools handle actions. Deep skills teach your agent how to plan scenes, choose effects, and review its own output.
Build repeatable rendering into your product with the SDK, REST API, templates, webhooks, and a deterministic composition contract.
Connect a trigger to a template, render variations at scale, and deliver the finished file where your team already works.
Install the domain knowledge that helps an agent choose a structure, respect timing, pick compatible effects, and review its own work.
Use the direct agent interface or connect your existing automation stack.
Install once. Give it a brief. Get a video back.