Hooks: nine pipeline hooks, every tool
Choose a hook, MCP for instance, to see what every tool in the register documents about it, beside the sentence from its page. Pages under a hook look at one tool closely. As of 2026-09-25.
The hooks follow a clip through a pipeline: calling the tool, what comes back, and what happens after.
A tool whose pages are silent on a hook gets a row that says so.
Hand-off to editing software and subtitle files are the hooks fewest tools document.
Single-tool pages exist where the documentation says enough to stand alone.
Teams building on a platform should start with the API and agent hooks; editors should start with hand-off and formats.
Each hook page links onward to the other eight, so a gap in one can be checked against the rest.
1Pages in this section
- Agents — Agent and automation hooks across 28 AI video tools and model platforms, as their own documentation states it, read 2026-09-25.
- API — Public API across 28 AI video tools and model platforms, as their own documentation states it, read 2026-09-25.
- Download — The finished file across 28 AI video tools and model platforms, as their own documentation states it, read 2026-09-25.
- Formats — File formats named across 28 AI video tools and model platforms, as their own documentation states it, read 2026-09-25.
- Hand-off — Hand-off to editing software across 28 AI video tools and model platforms, as their own documentation states it, read 2026-09-25.
- Resolution — Highest resolution named across 28 AI video tools and model platforms, as their own documentation states it, read 2026-09-25.
- SDKs — Official SDKs across 28 AI video tools and model platforms, as their own documentation states it, read 2026-09-25.
- Subtitles — Subtitle files across 28 AI video tools and model platforms, as their own documentation states it, read 2026-09-25.
- Webhooks — Finished-job signal across 28 AI video tools and model platforms, as their own documentation states it, read 2026-09-25.
2A pipeline stage, described
Read against “Hooks”, this is how SceneMixer describes the matching stage of its own pipeline:
That is SceneMixer's core design: characters live in a persistent asset library with locked reference art, and every segment that features a character is generated against those references — same face in episode 1 and episode 50.
SceneMixer, The AI Micro Drama Production Pipeline — “Can AI keep the same actors across 50 episodes?” (read 2026-10-13)
The cast is generated once, at the start, as full-body reference sheets. Every segment that features a character is generated against that character's sheet, with face and body crops attached as references — so the face in episode 1 is the face in episode 40.
SceneMixer, AI Short Drama Generator — “How does it keep the same actor across episodes?” (read 2026-10-13)