HappyHorse 1.1 Video Edit: AI Video Editor

Happy Horse 1.1 Video Edit modifies an existing video using a natural-language instruction, with selectable 720p/1080p output resolution. Happy Horse 1.1 Video Edit — modify an input video using natural-language instructions with optional reference images. Selectable output resolution (720p/1080p) — price scales with the resolution chosen.

Interactive model controls

Happy Horse 1.1 Video Edit — modify an input video using natural-language instructions with optional reference images. Selectable output resolution (720p/1080p) — price scales with the resolution chosen.

📝

Overview

About this model

Updated Sep 11, 2026

Happy Horse 1.1 Video Edit modifies an existing video using a natural-language instruction, with optional reference images to guide the edit, at your choice of 720p or 1080p output resolution. Note: Happy Horse 1.1 has no dedicated video-edit model of its own — requests are submitted directly via the Happy Horse 1.0 video-edit path (same webhook), so pricing matches Happy Horse 1.0's video-edit rates rather than 1.1's cheaper text/image/reference rates.

A single resolution parameter lets you draft cheaply at 720p and switch to 1080p for final output on the same endpoint.

1Subject replacement: swap a person, animal, or object in an existing video for something else
2Environment restyling: change the setting/background of a video while preserving action and camera motion
3Style transfer edits: apply an artistic or thematic restyle to existing footage
4Asset localization: swap in branded assets/products into existing video content
5Creative remixing: reimagine existing footage with new visual elements guided by reference images
💰

Pricing & Value

Cost analysis

muapiapp$0.21–$0.42/sec of input video (720p–1080p)

Simple per-second, resolution-scaled pricing with no subscriptions. Pick 720p for cost-effective drafts or 1080p for premium output, on the same endpoint.

** Competitor pricing is estimated based on similar model architectures and usage tiers.

⚙️

Technical Details

Configuration schema

Promptstring

Edit instruction describing the change to apply to the video.

Default ValueReplace the horse with @image1 and replace the shopping cart with @image2 while preserving the original high-speed motion and camera movement.
ResolutionEnum (2 options)

Output resolution. Price scales with resolution: 720p is cheaper, 1080p is more expensive.

Default Value720p
Video URLstring

Source video URL. MP4/MOV (H.264 recommended), 3-60s, <=100 MB, longer side <=2160px, shorter >=320px, frame rate >8 fps.

Default Valuehttps://d3adwkbyhxyrtq.cloudfront.net/webassets/videomodels/happy-horse-1-reference-to-video-720p.mp4
Reference Imagesarray

Optional 0-5 reference image URLs to guide the edit.

Default Valuehttps://d3adwkbyhxyrtq.cloudfront.net/webassets/videomodels/happy-horse-1-video-edit-1080p-1.jpg
Audio SettingEnum (2 options)

Audio strategy: 'auto' lets the model decide, 'origin' preserves source audio.

Default Valueauto
Seedint

Optional random seed for reproducibility (0-2147483647).

Default Value0
📖

Implementation Guide

Developer documentation

  1. Provide the source video_url (MP4/MOV, 3-60s, ≤100MB, longer side ≤2160px, shorter side ≥320px, >8fps).
  2. Write a prompt describing the edit instruction.
  3. Optionally add 0-5 reference images in images_list to guide the edit.
  4. Set resolution to "720p" (cheaper, default) or "1080p" (premium output).
  5. Choose audio_setting ("auto" or "origin") and an optional seed.
  6. Submit your request—the model applies the edit at the selected resolution.

Common Questions

Frequently asked

What is the cost of Happy Horse 1.1 Video Edit?

Happy Horse 1.1 Video Edit costs $0.21/sec of input video at 720p (default) or $0.42/sec at 1080p on muapi — the same rate as Happy Horse 1.0's video-edit, since 1.1 routes video-edit requests through the same underlying model.

How do I choose the resolution?

Pass `resolution: "720p"` (default) or `resolution: "1080p"` in your request body — both are served by the same endpoint.

What video formats are supported?

MP4 or MOV (H.264 recommended), 3-60 seconds, up to 100MB, longer side up to 2160px, shorter side at least 320px, frame rate above 8fps.

What does audio_setting control?

"auto" lets the model decide how to handle audio for the edit; "origin" preserves the source video's original audio track.

What happened to the dedicated 720p/1080p endpoints?

They still work exactly as before, unchanged, for existing integrations. This unified endpoint is the new recommended way to access both resolutions through one integration.