Does HappyHorse 1.0 Image-to-Video support zero data retention?

Not by default. See the per-route data-handling section for each route's logging stance and retention window.

Where is HappyHorse 1.0 Image-to-Video hosted?

HappyHorse 1.0 Image-to-Video is available on multi-region hosting through the qynio gateway. See the per-route table for details.

Is HappyHorse 1.0 Image-to-Video trained on prompts and outputs?

No. Every hosting route for HappyHorse 1.0 Image-to-Video is configured so customer prompts and outputs are not used to train models by default.

Is a no-KYC deposit available for HappyHorse 1.0 Image-to-Video?

Yes. A no-KYC Data Processing Agreement is available on at least one route serving HappyHorse 1.0 Image-to-Video. Contact hello@qyn.io to receive it.

HappyHorse 1.0 Image-to-Video

by Alibaba

HappyHorse 1.0 Image-to-Video is the image-conditioned member of Alibaba's HappyHorse family, a cinematic video generator that surfaced in April 2026 after an anonymous run to the top of the Artificial Analysis video arena. The model produces picture and audio together in one pass, so ambient sound, effects, and lip-synced speech land in step with the motion rather than being layered on afterward. Given a first-frame image and a text description of the intended motion, it carries the frame's look and lighting into a moving shot of 3 to 15 seconds. That makes it a fit for animating product stills, bringing key art to life, and turning storyboard frames into finished 720p or 1080p footage.

Open in playground Try in chat Compare

Key info

Input

Output

Features

Pricing

from $0.14 / sec

Billing

Per second

No training by default
no-KYC deposit available

Pricing

Usage-based pricing, billed by the second and tiered by variant, not by token.

Variant	Price
1080p	$0.24 / sec
720p	$0.14 / sec

Available routes

HappyHorse 1.0 Image-to-Video runs on 1 route through the qynio gateway. Compare residency, zero retention, and training posture at a glance — full data-handling detail per route below.

Provider	Region	Zero data retention	Training	Price
Alibaba Cloud	Multi	Not by default	No	from $0.14 / sec

Uptime and availability

HappyHorse 1.0 Image-to-Video runs on a single route through the qynio gateway today, so its availability is that provider's availability.

100%route uptime, last 30 days

Single route, no failover target within this model.

Name a second model in the same request and the gateway tries it on retriable errors, so a busy hour never has to reach your users. .

Measured over the last 30 days from each provider's official status feed via StatusGator. Refreshed hourly. See uptime for every provider qynio monitors.

Data handling per route

Each route hosting HappyHorse 1.0 Image-to-Video has its own privacy posture, residency, and no-KYC terms. Postures are maintained by qynio with a last-verification timestamp.

Alibaba Cloud — Multi-region

Zero data retention is not on by default — abuse monitoring. No training on customer data. GLOBAL; wallets; deposit available.

Zero data retention: Not by default — abuse monitoring. Derived from the logging and moderation facts.
Training: No training on customer data.
Logging: Abuse monitoring
Moderation: Not established
Caching: Not established
Subprocessor access: Not established
no-KYC deposit: deposit available
Transfer mechanism: wallets

Get started

Call HappyHorse 1.0 Image-to-Video through the qynio gateway with one API key. Let your coding agent set it up, or call it directly — qynio is drop-in compatible with the OpenAI, Anthropic, and Google AI SDKs.

Set it up with your agent

Copy this and paste it into a coding agent like Claude Code, Cursor or Codex and it'll wire up qynio for you.

Or call it directly

1import OpenAI from "openai";
2
3const client = new OpenAI({
4  apiKey: process.env.QYN_API_KEY,
5  baseURL: "https://api.qyn.io/v3/compat",
6});
7
8const completion = await client.chat.completions.create({
9  model: "alibaba:global/happyhorse-1.0-i2v",
10  messages: [{ role: "user", content: "Hello" }],
11});
12console.log(completion.choices[0].message.content);