HappyHorse MCP
Generate and edit videos using HappyHorse in the AI Agent through MCP.
Use a stable REST API for text-to-video, first-frame image-to-video, reference image-to-video, and video editing. Ideal for integrating creative storyboards, product assets, character references, and post-production workflows into your own product.
No need to piece together workflows across multiple vendor APIs—HappyHorse consolidates common video generation and editing modes into a unified request structure.
Enter shot descriptions, scenes, and actions to quickly generate short video prototypes.
Use a fixed first frame to control composition and bring static visual assets to life naturally.
Use multiple reference images to constrain characters, props, styles, and visual elements.
Use input videos and reference images for style transfer, outfit changes, and local replacement.
curl -X POST 'https://api.acedata.cloud/happyhorse/videos' \
-H 'authorization: Bearer YOUR_API_KEY' \
-H 'accept: application/json' \
-H 'content-type: application/json' \
-d '{
"action": "image_to_video",
"model": "happyhorse-1.1-i2v",
"image_url": "https://cdn.acedata.cloud/b1c82e4937.png",
"prompt": "A cinematic white horse lifts its head, the mane moves gently in the sunrise wind, slow camera push in, warm film lighting",
"resolution": "720P",
"duration": 5,
"async": true
}'Use async to immediately return a task ID, then query the result through /happyhorse/tasks; if callback_url is provided, the final result will be pushed to your service after the task is completed.
Text-to-video, image-to-video, reference images, and editing all use the same endpoint.
Images and videos must be publicly accessible URLs; using Ace Data Cloud CDN is recommended.
Use task_id to obtain the final CDN video URL, duration, and resolution.
From marketing assets to content tools, HappyHorse is better suited as a reliable video capability module rather than a one-time toy.
Quickly generate short clips of products, characters, and scenes from text and first frames to validate visual direction.
Use multiple reference images to lock in characters, clothing, props, and visual style.
Apply style transfer, local replacement, and audio preservation strategies to existing clips.
Reuse Ace Data Cloud's unified authentication, billing, task, and callback model for a clear and controllable integration path.
Create an application in the console to obtain a unified Bearer Token.
Provide prompt, image_url, image_urls, or video_url according to the action.
Get a downloadable CDN video URL through the task API or callback.
Consolidate model calls, task polling, CDN transfer, error classification, and billing records on the platform side.
| Capability | Ace Data Cloud HappyHorse | Some Others |
|---|---|---|
| Multiple video actions | Unified /happyhorse/videos | Multiple APIs to combine yourself |
| Result files | Automatic CDN transfer | Temporary URLs commonly expire |
| Billing | Recorded by actual seconds | Requires building your own usage ledger |
| Failure handling | Structured error codes | Upstream error formats are inconsistent |
1.1 models are prioritized for generation tasks; video editing currently uses 1.0 video-edit.
The default text-to-video model, suitable for generating short videos from scripts and shot descriptions.
Controls composition and visual tone with a first-frame image, suitable for animating product and character images.
Uses multiple reference images to constrain characters and props, suitable for scenarios with higher consistency requirements.
Edits based on input video, with the option to preserve the original audio.
Failed tasks are not billed; video editing is billed based on the combined input and output duration returned by the upstream provider.
The parameters, assets, and billing questions you are most likely to care about before launch.
Text-to-video only requires a prompt; first-frame image-to-video requires image_url; reference image-to-video requires 1–9 image_urls; video editing requires video_url, with an optional 0–5 reference images.
Ace Data Cloud transfers upstream results to the platform CDN, and the CDN URLs used in the documentation and API responses are accessible.
It is recommended to use async or callback_url. The API will first return a task_id, which you can actively query through /happyhorse/tasks or wait for a callback.
No. Only tasks that complete successfully and have recorded results are billed based on duration and resolution.
If you need different model ecosystems or more specialized video capabilities, you can combine these public services.
Use unified Tokens, unified billing, and unified task queries to reliably integrate video generation and editing capabilities into your application.