Skip to main content
AskEditor turns raw video into finished, directed edits through one API. An agent (or your code) names a template, hands over material, and gets back a finished edit. What “finished” means is stated on every template as its delivery:
  • delivery: "file" — an mp4 at finalUrl, plus canvasUrl: the same edit as an editable timeline in the AskEditor editor. Not a screenshot of the result: the layers, trims, animations and audio, live and adjustable.
  • delivery: "canvas" — the editable timeline is the deliverable, and there is no mp4. These templates sell an arrangement rather than pixels — which word, when, in what layer order — and it stays adjustable. Export it yourself when you want a file.
No other video API returns the second one, and the canvas templates exist because of it. How delivery works.

​
Start here

Quickstart for agents (MCP)

One config block connects Claude, Cursor, or any MCP client. Most integrations start (and finish) here.

Quickstart (REST)

Key → upload → run → poll, in curl, JavaScript, or Python.

Templates

The catalog. Each template is a finished edit with a typed input contract: what to record, the knobs, the price, the ETA.

The editable canvas

Why every response carries a timeline, and what your users can do with it.

​
The shape of every call

Templates are addresses, not endpoints: the API surface never grows as the catalog does. List them at GET /v1/templates or via the list_templates MCP tool.