About Magic Hour
Magic Hour is an AI media creation platform for generating and editing images, videos, and audio through a unified API.
Describe what should happen in Magic Hour, and when, in plain words. Whenever builds the workflow and runs it on a schedule, on a webhook, or when another app sends an event.
Connection requirements, provider permissions and optional AI usage apply. Read the runtime limits.
Magic Hour is an AI media creation platform for generating and editing images, videos, and audio through a unified API.
Through its API, using the credentials and permissions required by the provider.
Connect Claude, Cursor or Codex to the Whenever MCP server and your coding agent can build and deploy the Magic Hour workflow. It runs on Whenever afterwards, on its schedule or webhook, with the chat closed.
Set up the Whenever MCP serverMagic Hour bundles many AI media tools behind one API key: text-to-video, image-to-video, animation, lip sync, face swap, AI headshots, image upscaling, background removal, AI images and more. Automating it makes sense when the same kind of asset is needed repeatedly: a talking-head clip for each product update, consistent headshots for every new hire, upscaled versions of each uploaded product photo.
Every generation is a job rather than an instant answer. A workflow submits a request with its settings and inputs, receives a project id, then checks the video or image project until its status is complete, at which point the response includes download links for the output. Video jobs can take minutes, and the downloads should be copied to your own storage, because they are not meant as permanent hosting. Inputs such as source photos or audio are uploaded first through the API's upload URL step.
Each generation spends Magic Hour credits, and the cost depends on the tool and output; each project reports its credits charged, which for video is an estimate until the job completes and is refunded if it fails. A batch run over a sheet of fifty rows can therefore use a lot of credit, so cap the number of jobs per run and record which rows are done. Generated media also varies from run to run even with the same inputs, so plan for a person to review clips before they go public.
Face swap, lip sync and headshot tools work with people's likeness. Only process photos and voices of people who have agreed, and record that consent next to each row the workflow handles.
Authored starter briefs to configure with your accounts, not preconfigured workflows.
Event-driven: a new image in a folder becomes an upscaled copy in another.
Generates a lip-synced clip for review rather than publishing it automatically.
Runs once per person and stores the outputs for HR to choose from.
It checks the project by id; statuses move through queued and rendering to complete, error or canceled. Completed projects include signed download links for the generated files.
Each job spends credits that vary by tool and output. For video the charge shown while rendering is an estimate, final once complete, and refunded if generation fails.
Yes. The download links are signed and carry an expiry time, so copy files to storage you control, such as a Drive folder.
Only with their permission. Build the workflow so it skips anyone without a recorded consent, as the headshot example does.
Describe your first workflow in plain words. One stays live for free, no credit card.
No credit card required