API and MCP recipes

Durable project from an application

1. Upload owned media with POST /api/v2/media.
2. Create the source with POST /api/v2/projects.
3. Save updates with the current version in If-Match or the body version field.
4. Queue POST /api/v2/projects/{id}/renders with an idempotency key.
5. Receive render.completed or poll the render resource.

One temporary result

Use POST /api/v2/renders with an inline source when nobody needs to reopen or iterate on the project. Large media still belongs in the media API.

Repeatable template

1. Build and visually approve a durable project.
2. Publish a template.
3. Discover /inputs.
4. Render one variant.
5. Submit a bounded JSON or CSV batch after the test passes.

Agent-created project

1. Read jsoncut://v2/authoring-guide and the current project context.
2. Optionally create or update cut.md when a new direction or multi-scene build benefits from a persistent Agent brief.
3. Resolve media and author one bounded section.
4. Validate and request visual evidence.
5. Repair the smallest concrete finding and render the pinned version.

Exact request bodies and responses remain in the interactive V2 API reference; focused Agent tools are listed under MCP tools.