HappyHorse 1.1 R2V: Complete Specifications, Pricing, API Access & Use Cases (2026)
HappyHorse 1.1 R2V is Alibaba’s reference-to-video AI model for generating short clips using multiple reference images and written instructions. Its main improvement over version 1.0 is stronger visual consistency across characters, objects, and scene styles. According to the June 22, 2026 Gate.AI listing, it supports 3–15-second videos at resolutions up to 1080p. This guide examines its October 2026 pricing, specifications, production workflows, limitations, and API access. It is intended for developers, animation studios, advertising teams, and creators who need greater control over visual identity when producing AI-generated video.
What Is HappyHorse 1.1 R2V?
HappyHorse 1.1 R2V is the reference-to-video variant of Alibaba’s HappyHorse 1.1 generative video family. It transforms reference images and text instructions into short animated video sequences.
Alibaba Cloud records the release of HappyHorse 1.1 R2V on June 16, 2026, while the Gate.AI model card lists June 22, 2026. These dates refer to separate provider and platform records.
The defining improvement is stronger subject and style consistency compared with HappyHorse 1.0 R2V.
Alibaba describes version 1.1 as improving stability across characters, scene composition, cinematic motion, and visual appearance.
For example, creators can provide images of a fictional character, clothing accessories, and an environment. The prompt specifies how these elements should interact within the generated scene.
Unlike HappyHorse T2V, which generates footage from text alone, R2V uses visual references to help establish appearance.
What Are HappyHorse 1.1 R2V’s Key Specifications and Pricing?
Gate.AI and Alibaba Cloud document the following specifications.
| Specification | Details |
|---|---|
| Developer | Alibaba |
| Model | HappyHorse 1.1 R2V |
| Model type | Reference-to-video |
| Gate.AI catalog ID | alibaba/happyhorse-1.1-r2v |
| Gate.AI API model ID | happyhorse-1.1-r2v |
| Alibaba release record | June 16, 2026 |
| Gate.AI listing date | June 22, 2026 |
| Inputs | Reference images and text |
| Reference image limit | 1–9 images |
| Output | Generated video |
| Video duration | 3–15 seconds |
| Maximum resolution | 1080p |
| Input image formats | JPEG, PNG, WEBP |
| Context window | Not specified |
| Input token price | Not separately listed |
| Cache pricing | Not listed |
| Gate.AI 720p pricing | $0.123769/second |
| Gate.AI 1080p pricing | $0.165026/second |
Alibaba Cloud also documents a 480p option for direct access, but Gate.AI’s published pricing table specifies 720p and 1080p rates.
How Much Does HappyHorse 1.1 R2V Cost?
Gate.AI charges per generated video second, with separate rates for 720p and 1080p.
| Duration | 720p estimated cost | 1080p estimated cost |
|---|---|---|
| 3 seconds | $0.37 | $0.50 |
| 5 seconds | $0.62 | $0.83 |
| 10 seconds | $1.24 | $1.65 |
| 15 seconds | $1.86 | $2.48 |
For a 10-second 1080p video:
Estimated cost = 10 × $0.165026 = $1.65026
Generating 50 such clips would cost approximately $82.51 at the listed rate.
Importantly, version 1.0 R2V lists $0.220034 per second for 1080p. Version 1.1’s rate is approximately 25% lower.
These estimates exclude any additional charges and should not be confused with Alibaba Cloud’s provider-direct pricing.
What Can HappyHorse 1.1 R2V Do That Makes It Useful in Production?
Maintain More Consistent Characters Across Frames
Character consistency is the model’s central production advantage.
Reference images help establish appearance, clothing, facial characteristics, and other recognizable visual details.
Alibaba describes version 1.1 as providing improved subject stability compared with the earlier release.
For a fictional-character campaign, this can reduce the need to redesign a character’s appearance for every scene, although output validation is still necessary.
Combine Multiple Visual References
The model supports up to nine images per generation.
A production team can supply character artwork, wardrobe details, and background references, then explain how these elements should appear together.
Alibaba’s API documentation supports referencing images individually in the prompt using identifiers such as [Image 1] and [Image 2].
This is useful when visual requirements are distributed across different creative assets.
Support Shot-Based Production
HappyHorse 1.1 R2V generates clips lasting 3–15 seconds.
Teams can create several short shots around an established character or visual identity and assemble approved results in an editing application.
This supports storyboarding, creative iteration, and modular video production without implying automatic continuity across separate generations.
What Are HappyHorse 1.1 R2V’s Supported Modalities?
The model combines image and text inputs to produce video.
| Modality | Input support | Output support | Details |
|---|---|---|---|
| Text | Yes | No | Scene and motion instructions |
| Reference images | Yes | No | 1–9 reference images |
| JPEG/JPG | Yes | No | Supported reference format |
| PNG/WEBP | Yes | No | Supported reference formats |
| Video | No | Yes | 3–15-second generated clips |
| Resolution | — | Yes | Up to 1080p |
| Aspect ratio | Configuration | Yes | Landscape, portrait, square and other supported formats |
| Audio | Not documented as input | Not confirmed for this variant | Requires separate model-specific verification |
Alibaba’s direct API documents reference-image requirements, including a maximum image size of 20 MB and a minimum shortest-side resolution of 400 pixels.
These provider requirements should not automatically be assumed identical to Gate.AI’s media-submission restrictions.
Where Does HappyHorse 1.1 R2V Fall Short?
Short generation duration: The 15-second maximum means longer videos require additional editing or multiple generations.
Consistency is not absolute: Improved reference handling does not guarantee identical faces, clothing, proportions, or visual details during difficult motion sequences.
Reference quality matters: Low-resolution or unclear images can reduce the usefulness of visual guidance.
Multiple-reference complexity: Images containing conflicting appearances or styles may make the desired result harder to communicate.
API differences: Alibaba Cloud and Gate.AI document different request structures. Code written for one platform should not be assumed compatible with the other.
Limited public performance evidence: The available documentation does not establish quantitative improvements in generation latency or character-consistency accuracy.
Production teams should review outputs for visual continuity, accurate product representation, and appropriate permissions for reference images.
What Is HappyHorse 1.1 R2V Best Used For?
HappyHorse 1.1 R2V is particularly relevant when recognizable visual assets must guide generated footage.
Character-led advertising: Marketing teams can use established fictional characters across short promotional scenes while checking identity consistency.
Animated brand storytelling: Studios can incorporate approved visual references into scene generation to support a recognizable campaign style.
Fashion and product concepts: Creative teams can combine character, clothing, and accessory references into short sequences. Exact commercial product reproduction still requires manual checking.
Storyboarding and previsualization: Filmmakers can explore compositions, actions, and camera movement around reference artwork before final production.
Choose HappyHorse 1.1 R2V when multiple visual references and subject consistency are important.
Consider T2V for text-only concepts, I2V for animating one starting image, or another video model when longer output is essential.
How Does HappyHorse 1.1 R2V Compare to HappyHorse 1.0 R2V and Wan 2.6 R2V?
These models support reference-guided video generation, but their reference mechanisms and production priorities differ.
| Feature | HappyHorse 1.1 R2V | HappyHorse 1.0 R2V | Wan 2.6 R2V |
|---|---|---|---|
| Developer | Alibaba | Alibaba | Alibaba |
| Reference type | Multiple images | Multiple images | Reference video |
| Maximum image references | 9 | 9 | Different reference mechanism |
| Main positioning | Improved character and style consistency | Earlier reference-guided workflow | Motion and camera guidance |
| Maximum resolution | 1080p | 1080p | 1080p |
| Maximum duration | 15 seconds | 15 seconds | 10 seconds |
| Gate.AI 1080p price | $0.165026/sec | $0.220034/sec | Check current model-specific pricing |
The most meaningful version change is between HappyHorse 1.0 and 1.1.
Both support multiple reference images, but Alibaba describes version 1.1 as offering greater subject and visual stability.
The newer version also has a lower listed 1080p generation price on Gate.AI.
Wan 2.6 R2V addresses a related but different requirement. Its reference-video workflow is designed around transferring motion, effects, and camera movement from existing footage.
For teams prioritizing motion reproduction, the Wan 2.6 R2V guide provides a more relevant comparison.
HappyHorse 1.1 R2V is more directly aligned with projects where reference images establish the desired character or scene appearance.
How Do I Access HappyHorse 1.1 R2V Through Gate.AI?
HappyHorse 1.1 R2V appears in the Gate.AI model catalog, with documented video-generation endpoints.
| API field | Value |
|---|---|
| Endpoint | https://api.gate.ai/api/v1/videos |
| Method | POST |
| Authentication | Bearer API key |
| Content type | application/json |
| Request model | happyhorse-1.1-r2v |
| Job retrieval | GET /api/v1/videos/{job_id} |
Gate.AI documents an optional input_references parameter for reference media, but its published example does not establish the exact reference-image object schema for this variant.
Therefore, the following examples demonstrate the documented video-job submission and retrieval structure. They are not complete reference-guided generation requests until the required image-reference fields have been validated.
Python Example
import osimport requestsapi_key = os.environ["GATEAI_API_KEY"]endpoint = "https://api.gate.ai/api/v1/videos"headers = {"Authorization": f"Bearer {api_key}","Content-Type": "application/json"}payload = {"model": "happyhorse-1.1-r2v","prompt": ("A fictional character walks through ""a cinematic city street, smooth camera ""movement, consistent clothing and style"),"duration": 6,"resolution": "720p","aspect_ratio": "16:9"}# Add input_references using the validated Gate.AI# media schema before production R2V generation.response = requests.post(endpoint,headers=headers,json=payload,timeout=60)response.raise_for_status()job_id = response.json()["data"]["job_id"]result = requests.get(f"{endpoint}/{job_id}",headers=headers,timeout=60)result.raise_for_status()print(result.json())
This code illustrates task submission and an initial status check. It does not implement repeated polling or provide a complete multi-image request.
curl Example
export GATEAI_API_KEY="YOUR_API_KEY"curl --location \"https://api.gate.ai/api/v1/videos" \--header "Authorization: Bearer $GATEAI_API_KEY" \--header "Content-Type: application/json" \--data '{"model": "happyhorse-1.1-r2v","prompt": "A cinematic character scene with smooth motion and consistent visual style","duration": 6,"resolution": "720p","aspect_ratio": "16:9"}'
The example uses Gate.AI’s documented base video request. Reference-image generation additionally requires a correctly structured input_references field, which should be confirmed before execution.
Alibaba Cloud documents a complete provider-direct multi-image workflow, but its nested input.media structure must not be substituted into the Gate.AI request without verification.
Both examples are untested illustrations of the Gate.AI job workflow. Developers should consult the current Gate.AI developer documentation for media requirements, asynchronous job handling, and output retrieval.
FAQs
What is HappyHorse 1.1 R2V?
HappyHorse 1.1 R2V is Alibaba’s reference-to-video model that generates short clips from multiple reference images and text instructions, with improved visual consistency compared with version 1.0.
How many reference images does HappyHorse 1.1 R2V support?
Alibaba Cloud documents support for one to nine reference images per generation.
Is HappyHorse 1.1 R2V cheaper than version 1.0?
At 1080p, yes. Gate.AI lists version 1.1 at $0.165026 per second compared with $0.220034 for version 1.0, approximately 25% lower.
What is the maximum video duration?
HappyHorse 1.1 R2V generates clips lasting between 3 and 15 seconds.
Does HappyHorse 1.1 R2V guarantee character consistency?
No. Alibaba describes stronger consistency than version 1.0, but complex scenes and motion may still require manual review and regeneration.
Can developers use HappyHorse 1.1 R2V through an API?
Yes. Gate.AI documents video-job submission and retrieval. Developers must confirm the reference-image payload schema before implementing the complete multi-image generation workflow.


