Adobe Firefly and Replicate: pipeline hooks
Adobe Firefly and Replicate document different things on five of the nine hooks: API access, agent hooks, downloads, SDKs and job signals. From 5 source pages, read 2026-09-25; no maker pays to be listed.
| Feature | Adobe Firefly | Replicate |
|---|---|---|
| Public API | An API for its own models | One API for many providers |
| Agent and automation hooks | Not documented in the docs read | An MCP connection |
| Highest resolution named | Not documented in the docs read | Not documented in the docs read |
| Hand-off to editing software | Not documented in the docs read | Not documented in the docs read |
| Subtitle files | Not documented in the docs read | Not documented in the docs read |
| The finished file | Not documented in the docs read | A link or file that expires |
| File formats named | Not documented in the docs read | Not documented in the docs read |
| Official SDKs | Not documented in the docs read | SDKs in two or more languages |
| Finished-job signal | A status polled until done | A webhook or callback URL |
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
Replicate documents agent hooks, downloads and SDKs, which Adobe Firefly's pages leave out. For API access, Adobe Firefly names an API for its own models and Replicate one API for many providers. For job signals, Adobe Firefly names a status polled until done and Replicate a webhook or callback URL. Neither documents resolution, editing hand-off, subtitle files or file formats.
2From each tool's documentation
Public API
The Adobe Firefly API makes it easy for you to integrate generative AI into your creative workflows
Adobe, Firefly API overview
Run and fine-tune models. Deploy custom models. All with one line of code.
Replicate, home page
The finished file
Adobe Firefly's documentation read says nothing here.
are automatically removed after an hour, by default
Replicate, documentation: data retention
Finished-job signal
repeatedly polls statusUrl to see when Firefly completes the job
Adobe, Firefly API: using the asynchronous API
Sending notifications when long-running predictions finish.
Replicate, documentation: webhooks
- OverviewAn API for building Firefly's generative AI into creative workflows
- Page headerOne API for running many makers' models and custom ones
- Automatic data clean upOutput files from API predictions removed after an hour by default
- Checking job statusAsync jobs whose status URL is polled until they succeed or fail
- About webhooksWebhooks that deliver a finished prediction's metadata and output
3A third tool on getting the file out, beside Adobe Firefly and Replicate
| Field | SceneMixer | Source |
|---|---|---|
| The finished file | A full-quality download and a share link; the browser plays a lighter copy | SceneMixer, 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.