How AI video tools plug into a production pipeline

{
  "api": "An API for its own models",
  "agents": "A command-line tool",
  "res": "1080p",
  "handoff": "Not documented in the docs read",
  "subs": "Not documented in the docs read",
  "download": "A link or file that expires",
  "formats": "MP4",
  "sdk": "One SDK or client",
  "webhook": "A status polled until done"
}

1Reference: the nine hooks

Each hook has its own page with every tool's reading and the words behind it. The code name is the key the register uses in its CSV.

• apiPublic API25 of 28 tools document it
• agentsAgent and automation hooks14 of 28 tools document it
• resHighest resolution named21 of 28 tools document it
• handoffHand-off to editing software4 of 28 tools document it
• subsSubtitle files4 of 28 tools document it
• downloadThe finished file15 of 28 tools document it
• formatsFile formats named8 of 28 tools document it
• sdkOfficial SDKs9 of 28 tools document it
• webhookFinished-job signal23 of 28 tools document it

2The tools

Each card lists the hooks a tool's own documentation states. Open one for all nine, quoted and dated.

• AFAdobe Fireflymodel makerAPIWebhooks
• BMBytePlus ModelArkmodel platformAPIFormatsWebhooks
• CoColossyanavatar videoAPIWebhooks
• DID-IDavatar videoAPIAgentsDownloadWebhooks
• DeDescriptvideo editorAPIAgentsResolutionHand-offSubtitlesWebhooks
• Fafalmodel platformAPIResolutionDownloadSDKsWebhooks
• FlFlixlycreative suiteAPIAgentsResolutionSDKsWebhooks
• GVGoogle Veomodel makerAPIResolutionDownloadSDKsWebhooks
• HeHeyGenavatar videoAPIAgentsSubtitlesDownloadFormatsWebhooks
• HiHiggsfieldcreative studioAPIAgentsResolutionDownloadSDKsWebhooks
• Ininvideovideo makerResolutionHand-off
• KaKapwingvideo editorResolutionSubtitles
• KAKling AImodel makerAPIAgentsResolutionDownloadWebhooks
• KrKreacreative suiteAPIAgentsWebhooks
• LtLTXmodel makerAPIResolutionHand-offDownloadFormatsWebhooks
• LuLumamodel makerAPIResolutionHand-offFormatsSDKsWebhooks
• MiMiniMaxmodel makerAPIAgentsResolutionDownloadWebhooks
• OSOpenAI Soramodel makerAPIResolutionDownloadFormatsWebhooks
• PiPikavideo appAPIResolution
• PiPixVersemodel makerAPIResolutionDownloadWebhooks
• ReReplicatemodel platformAPIAgentsDownloadSDKsWebhooks
• ReRevidvideo makerAPIAgentsResolutionWebhooks
• RuRunwaymodel makerAPIAgentsResolutionDownloadSDKsWebhooks
• ScSceneMixerdrama appResolutionSubtitlesDownload
• SySynthesiaavatar videoAPIAgentsResolutionDownloadFormatsWebhooks
• VeVEEDvideo editorAPIResolutionFormatsSDKsWebhooks
• ViVidumodel makerAPIAgentsResolution
• WaWan (Alibaba Cloud)model makerAPIAgentsResolutionDownloadFormatsSDKsWebhooks

3How often each hook is documented

Inclusion rule. The 28 tools in the register; a hook counts when the tool's own documentation states it. Order. The order hooks take on every tool page.

4Why the pipeline matters

A generated clip is the start of the work, not the end. It has to reach an editor, pick up subtitles, be graded, conformed and delivered in a format a platform or a broadcaster accepts. A tool that documents how its output leaves it saves that work; one that does not leaves it to guesswork.

For teams building their own tools, the question comes earlier: can the model be called from code, can an agent drive it, and how will the pipeline know when a render is done?

5What the register finds

D-ID, Descript, Flixly, HeyGen, Higgsfield, Krea, MiniMax, Replicate, Revid, Runway, Synthesia and Vidu document an MCP connection for agents. Only Descript, invideo, LTX and Luma describe a hand-off to editing or finishing software.

Every reading is quoted from the tool's own documentation and dated. Developer platforms change fast; the current documentation always has the final say.

6Sections

• Tools
• Hooks
• Pairs
• Questions
• Terms
• Pipeline notes
• Data
• Pipeline fit — Runway, Morphic, Pollo and PixVerse, held against the nine hooks.
• Handoff rankings — Two rankings of AI video tools by whether their own pages spell out the handoff