Agent Edl
Natural language → a proposed edit of this timeline (#127). Gated on agentic.
PROPOSES ONLY — it never writes. The client shows the plan, and on confirm applies the returned EDL through its ordinary edit+save path. That is a deliberate design choice on three counts:
_EdlBodycarries no version/etag, so a server-side apply would race the editor’s autosave and silently clobber whatever the user typed while the model was thinking.- Applying client-side goes through the editor’s single
mutate()seam, so an agentic edit lands on the undo stack like any other — “undo” is the real confirm button. validate_edl+_reject_foreign_assetson PUT stay the only path an EDL takes into the database. This endpoint adds no new way to write one.
No asset check is needed here: an op cannot carry an asset_id (see ai/edl_agent), so every id in the output was already in the input the caller sent us, and the save path checks it regardless.
Path Parameters
Body
edl is the timeline AS IT IS ON SCREEN, not the saved one — the editor autosaves off by
default, so planning against the stored copy would silently ignore the user's unsaved edits.
ops re-applies a plan the user has already seen (and possibly pruned) without paying for a
second model call.
Response
Successful Response
The response is of type Response Agent Edl Api V1 Projects Public Id Edl Agent Post · object.