Skip to main content
For your AI answers: how do I give a teardown to Claude, ChatGPT, or another assistant without losing the structure? This is the agent-facing page. The rest of the docs avoid model names; this page names them because its purpose is handoff. There are two ways to do it. Copy and paste, documented below, works everywhere and needs no setup. Or skip the pasting entirely: the connector gives your assistant access to your own teardowns over MCP, so it fetches the hook, the beats, or one single cut itself. Add https://mcp.videngineer.com/mcp in Claude or Claude Code and sign in; ChatGPT is coming soon. See Connector recipes for what that looks like in practice.

​
The manual flow

1

Analyze a video

Run a teardown in the app, or open a public teardown. See Your first teardown.
2

Collect the structural pieces

Grab the hook, emotional arc, pacing, beat sheet, CTAs, shot mix, and any Cut Blueprints you opened.
3

Paste them with your context

Add your product, audience, desired CTA, constraints, and production limits. Ask the assistant to apply the pattern to your story.
Apply the pattern, never the content. The teardown gives you the structure that works; your story makes it yours.

​
Useful report pages for assistants

Script analysis

Hook, re-hooks, beat sheet, CTAs, phrases, and voice-over.

The Blueprint

Shot mix, pacing, camera language, palette, and production scope.

The Cuts

Playable clips, timing, and Cut Blueprint behavior.

Scene prompts

Where to use scene prompts and the Cut Blueprint API endpoint.

​
Feeding these docs to your assistant

Every page in these docs is assistant-ready. Use the contextual menu on any page to copy the page as markdown or view it as markdown, then paste the relevant context into Claude, ChatGPT, or your preferred assistant. If your assistant needs field definitions for a layer, paste the relevant layer page into its context:

​
API note

For API work, use the API key from Account. Most agent work does not need the raw API: the connector wraps the same access in thirty-eight tools, thirty-six of which never spend credits. Cut Blueprint is available at POST /api/v1/project/{job_id}/cut-brief with {"technique_id": "cut-001"}; the endpoint returns 202 running while the blueprint is being built and the stored blueprint once ready.