AIMovieToolkit

How AI video tools plug into a pipeline

Flixly and Google Veo: pipeline hooks

Flixly and Google Veo document different things on four of the nine hooks: agent hooks, resolution, downloads and job signals. From 3 source pages, read 2026-09-25; no maker pays to be listed.

Hooks each documentsSolid: documented. Outline: nothing read.Hooks each documentsFlixlyGoogle VeoPublic APIPublic API — Flixly: An API for its own modelsPublic API — Google Veo: An API for its own modelsAgent and automation hooksAgent and automation hooks — Flixly: An MCP connectionAgent and automation hooks — Google Veo: Not documented in the docs readHighest resolution namedHighest resolution named — Flixly: 1080pHighest resolution named — Google Veo: 4KHand-off to editing softwareHand-off to editing software — Flixly: Not documented in the docs readHand-off to editing software — Google Veo: Not documented in the docs readSubtitle filesSubtitle files — Flixly: Not documented in the docs readSubtitle files — Google Veo: Not documented in the docs readThe finished fileThe finished file — Flixly: Not documented in the docs readThe finished file — Google Veo: A link or file that expiresFile formats namedFile formats named — Flixly: Not documented in the docs readFile formats named — Google Veo: Not documented in the docs readOfficial SDKsOfficial SDKs — Flixly: SDKs in two or more languagesOfficial SDKs — Google Veo: SDKs in two or more languagesFinished-job signalFinished-job signal — Flixly: A webhook or callback URLFinished-job signal — Google Veo: A status polled until done
Fig. 1 Solid: documented. Outline: nothing read.
Flixly and Google Veo, feature by feature, read 2026-09-25.
FeatureFlixlyGoogle Veo
Public APIAn API for its own modelsAn API for its own models
Agent and automation hooksAn MCP connectionNot documented in the docs read
Highest resolution named1080p4K
Hand-off to editing softwareNot documented in the docs readNot documented in the docs read
Subtitle filesNot documented in the docs readNot documented in the docs read
The finished fileNot documented in the docs readA link or file that expires
File formats namedNot documented in the docs readNot documented in the docs read
Official SDKsSDKs in two or more languagesSDKs in two or more languages
Finished-job signalA webhook or callback URLA status polled until done

Inclusion rule. The nine hooks every tool in the register is read for. Order. The order hooks take on every tool page.

1Where they part

Flixly documents agent hooks, which Google Veo's pages leave out. Google Veo documents downloads, which Flixly's pages leave out. For API access the two match: an API for its own models. For resolution, Flixly names 1080p and Google Veo 4K. For SDKs the two match: sDKs in two or more languages. For job signals, Flixly names a webhook or callback URL and Google Veo a status polled until done. Neither documents editing hand-off, subtitle files or file formats.

2From each tool's documentation

Agent and automation hooks

Flixly is now an app in ChatGPT — connect it in one click

Flixly, home page

Google Veo's documentation read says nothing here.

Highest resolution named

all generated as one seamless video in 1080p

Flixly, home page

Veo 3.1 is a model for generating 8-second videos (720p, 1080p, or 4k) with natively generated audio.

Google, Gemini API documentation: Veo

Finished-job signal

Endpoints, parameters, webhooks and error codes.

Flixly, API page

Poll the operation status until the video is ready.

Google, Gemini API documentation: Veo

3A third tool on getting the file out, beside Flixly and Google Veo

What SceneMixer's page says on a field where Flixly and Google Veo differ, read 2026-09-25.
FieldSceneMixerSource
The finished fileA full-quality download and a share link; the browser plays a lighter copySceneMixer, guide to compositing and sharing an episode

Inclusion rule. Fields on which SceneMixer's pages state something; most toolkit fields are not its subject. Order. The order fields take on every tool page.

4More pairs with these tools