HappyHorse 1.1 T2V: Complete Specifications, Pricing, API Access & Use Cases (2026)
HappyHorse 1.1 T2V is a text-to-video generation model from Alibaba designed to convert written scene descriptions into short video clips. Gate.AI lists the model with 3–15 second generation, resolutions up to 1080p, and improved adherence to complex prompts compared with HappyHorse 1.0 T2V. This guide focuses on the specifications that matter to creators, developers, and product teams: pricing, duration, resolution, workflow fit, limitations, and documented API access as verified in September 2026.
What Is HappyHorse 1.1 T2V?
HappyHorse 1.1 T2V is the text-to-video, or T2V, member of Alibaba’s HappyHorse 1.1 video-generation family. Its input is a written description, and its core task is turning that description into a short generated video. Gate.AI dates the model to June 22, 2026 and describes version 1.1 as having stronger prompt adherence than HappyHorse 1.0 when instructions become more complex.
That version distinction matters. HappyHorse 1.0 T2V already supported 3–15 second clips up to 1080p, so version 1.1 is not primarily a duration or resolution upgrade. The documented differentiation is improved instruction following. Gate.AI also lists separate HappyHorse 1.1 I2V and R2V variants for workflows that start with an image or reference assets, respectively.
For teams starting purely from scripts or prompts, T2V therefore avoids adding reference media that the task does not require.
What Are HappyHorse 1.1 T2V’s Key Specifications and Pricing?
Gate.AI lists separate per-second rates for 720p and 1080p video generation. There is no token-style input charge or conventional LLM context window shown on the model card.
| Specification | Verified Value |
|---|---|
| Provider | Alibaba |
| Model type | Text-to-video generation |
| Release/listing date | June 22, 2026 |
| Catalog identifier | alibaba/happyhorse-1.1-t2v |
| Gate.AI request model ID | happyhorse-1.1-t2v |
| Video duration | 3–15 seconds |
| Maximum resolution | 1080p |
| 720p pricing | $0.123769 per generated second |
| 1080p pricing | $0.165026 per generated second |
| Token context window | Not applicable / not listed |
| Text input pricing | No separate charge listed |
| Cache pricing | Not listed |
The distinction between identifiers is worth noting: the Gate.AI model page displays the catalog identifier alibaba/happyhorse-1.1-t2v, while its documented API example submits happyhorse-1.1-t2v in the model field. Developers should use the value documented for the actual API request rather than substituting the catalog path.
A 10-second generation costs approximately $1.24 at 720p:
10 × $0.123769 = $1.23769
The same 10-second clip at 1080p costs approximately $1.65:
10 × $0.165026 = $1.65026
These are calculated estimates based on listed per-second rates, before retries or multiple creative variants.
What Can HappyHorse 1.1 T2V Do That Makes It Useful in Production?
Its most relevant production characteristic is direct script-to-video generation. A creative team can describe a subject, action, setting, camera treatment, and visual style, then generate a short clip without supplying an initial image.
The second useful characteristic is improved complex-prompt adherence relative to HappyHorse 1.0, according to the Gate.AI model card. This may matter when a shot contains several simultaneous instructions—for example, subject movement, camera movement, environment, framing, and aesthetic direction. The documentation does not publish a quantitative prompt-adherence benchmark, so the improvement should be treated as the platform’s model-positioning claim rather than a measured percentage gain.
The 3–15 second range also makes the model practical for modular production: teams can generate individual shots and assemble selected clips in an editing workflow rather than asking one generation to produce an entire long-form sequence.
What Are HappyHorse 1.1 T2V’s Supported Modalities?
| Modality | Support | Notes |
|---|---|---|
| Text input | Yes | Written prompt describes the generated scene |
| Image input | No for core T2V workflow | HappyHorse 1.1 I2V is the corresponding image-led variant |
| Reference-media input | Not established as a HappyHorse T2V capability | Gate.AI’s general video endpoint supports reference fields, but that does not prove support for this exact variant |
| Video output | Yes | 3–15 seconds, up to 1080p |
| Audio generation | Not specifically confirmed | The general Gate.AI video schema contains generate_audio, but the HappyHorse description does not independently document native audio capability |
This distinction prevents platform-wide API options from being mistaken for model-specific capabilities. Gate.AI’s video API supports a common schema covering multiple video models, while the selected model determines which options are actually supported upstream.
Where Does HappyHorse 1.1 T2V Fall Short?
The clearest limitation is duration. A maximum 15-second clip makes HappyHorse 1.1 T2V suitable for individual shots and short creative assets, not complete long-form videos without editing or sequencing.
Its public technical documentation is also relatively sparse. Gate.AI verifies resolution, duration, pricing, model positioning, and the API workflow, but does not publish model-specific benchmarks, latency figures, frame rate, architecture details, training data, fine-tuning support, or a quantified comparison of prompt adherence.
Another operational consideration is generation cost. A full 15-second 1080p clip costs about $2.48 at the listed rate. Ten alternative versions would therefore represent roughly $24.75 of generation before additional iterations. Production teams may benefit from testing prompts at 720p before producing selected versions at 1080p.
Generated media should also receive human review for visual consistency, brand accuracy, rights-sensitive material, and factual details before publication.
What Is HappyHorse 1.1 T2V Best Used For?
HappyHorse 1.1 T2V fits workflows where the creative direction already exists primarily as text: short advertising concepts, social-video shots, cinematic scene visualization, campaign drafts, story beats, and previsualization from scripts.
Choose it when text is the main source material, the target shot fits within 15 seconds, and following a more detailed prompt matters. If the workflow needs to animate an existing still image, HappyHorse 1.1 I2V is structurally a closer fit. If maintaining appearance from multiple references matters, the R2V variant is more relevant.
For teams evaluating broader alternatives, [Wan 2.6 T2V] and [Seedance 2.0] address overlapping AI-video workflows but expose different capabilities and pricing structures rather than serving as interchangeable versions of HappyHorse.
How Does HappyHorse 1.1 T2V Compare to HappyHorse 1.0 T2V and Wan 2.6 T2V?
| Area | HappyHorse 1.1 T2V | HappyHorse 1.0 T2V | Wan 2.6 T2V |
|---|---|---|---|
| Provider | Alibaba | Alibaba | Alibaba |
| Primary input | Text | Text | Text; documented audio support in applicable workflow |
| Duration | 3–15 sec | 3–15 sec | 2–15 sec |
| Resolution | Up to 1080p | Up to 1080p | 720p/1080p |
| 720p Gate.AI price | $0.123769/sec | $0.123769/sec | $0.10/sec |
| 1080p Gate.AI price | $0.165026/sec | $0.220034/sec | $0.15/sec |
| Main documented distinction | Stronger complex-prompt adherence vs 1.0 | Earlier HappyHorse T2V version | Audio-video generation and multi-shot positioning |
HappyHorse 1.1 is especially relevant to existing HappyHorse 1.0 users because the documented 1080p rate is lower while the model card also claims stronger complex-instruction adherence. Wan 2.6 T2V is a different selection path for teams that specifically require its documented audio-video workflow. This keeps the HappyHorse article focused on version-specific prompt-to-video behavior rather than duplicating the broader Wan 2.6 T2V topic.
How Do I Access HappyHorse 1.1 T2V Through Gate.AI?
Gate.AI documents video generation through an asynchronous API. Requests are submitted to POST /api/v1/videos with Bearer authentication. The service returns a job ID, which can then be checked through GET /api/v1/videos/{job_id} until generation completes.
Python
import osimport timeimport requestsapi_key = os.environ["GATEAI_API_KEY"]base_url = "https://api.gate.ai/api/v1/videos"headers = {"Authorization": f"Bearer {api_key}","Content-Type": "application/json"}payload = {"model": "happyhorse-1.1-t2v","prompt": "A futuristic train crossing a desert at sunset, wide cinematic shot","duration": 6,"resolution": "720p","aspect_ratio": "16:9","generate_audio": False,"seed": -1}response = requests.post(base_url, headers=headers, json=payload)response.raise_for_status()job_id = response.json()["data"]["job_id"]while True:status = requests.get(f"{base_url}/{job_id}", headers=headers)status.raise_for_status()data = status.json()["data"]if data["status"] in {"completed", "failed"}:print(data)breaktime.sleep(5)
cURL
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-t2v","prompt": "A futuristic train crossing a desert at sunset, wide cinematic shot","duration": 6,"resolution": "720p","aspect_ratio": "16:9","generate_audio": false,"seed": -1}'
The examples follow Gate.AI’s documented video endpoint and the model-specific request ID shown on the HappyHorse 1.1 T2V model card. They have not been execution-tested here.
FAQs
How long can HappyHorse 1.1 T2V videos be?
Gate.AI lists a supported clip duration of 3 to 15 seconds, making the model primarily suited to individual shots and short-form creative generation.
Does HappyHorse 1.1 T2V support 1080p?
Yes. Gate.AI lists output at up to 1080p, priced at $0.165026 per generated second as of September 2026. The listed 720p rate is $0.123769 per second.
What improved from HappyHorse 1.0 to 1.1?
The documented improvement is stronger adherence to complex prompts. Both versions generate 3–15 second clips up to 1080p, while the listed 1080p price is lower for version 1.1 than version 1.0.
Is HappyHorse 1.1 T2V suitable for long videos?
Not as a single-generation long-form model. Its documented maximum is 15 seconds, so longer productions require multiple generated shots followed by sequencing and editing.


