BaiLian

Happyhorse 1.1 R2v

AlibabaToken-based
Alias:happyhorse-1.1-r2v
Create API Key

Compare happyhorse-1.1-r2v API pricing, supported endpoints, capabilities and access options on voguesly.

视频生成主体一致性
Starting price
Input / Output · 1M
Context
—
Maximum input window
Modalities
→

Pricing by Supplier

标准按次
图片音频视频等多模态按次计费
Input/ 1M tokens
$75
Output/ 1M tokens
$75

Capabilities / Supported modalities

Function callingToolsJSON modeStructured outputVision
Input
Output

Provider & data privacy

Provider
Unknown
Tokenizer
BPE (vendor-specific)
License
Provider-specificUnknown
Data retention76 daysNot used for upstream training by default

Performance

Benchmarks

Scores on standardized evaluations. Higher percentages are better — and rank percentile shows

Metrics sourced fromArtificial Analysis 2026-09-30·Happyhorse 1.1 R2v

This model is not included in the current benchmark snapshot.

Missing models or measurements are not zero scores.

Benchmark charts preserve the source model selection and reasoning settings. Missing models or measurements are not zero scores, and benchmark cost or speed is not this site’s service commitment.

About Happyhorse 1.1 R2v

HappyHorse 1.1 参考图生视频适合已经有人物、商品或场景素材,但希望重新安排镜头内容的创作。它可以结合 1–9 张参考图生成新场景,让图片分别提供主体外观、环境和视觉风格,再由文字描述动作与镜头关系。

与把一张图片直接当作首帧不同,参考图更像为短片准备的素材资料。你可以让人物照片决定角色,让另一张图片决定服装或空间,再安排角色走入场景、使用商品或完成一个简单动作。提示中按顺序说明每张图片负责什么,能减少主体、背景和风格互相混淆。

这种方式适合系列人物短片、商品创意和故事分镜。连续生成不同场景时,可以复用同一组主体参考,明确重要特征与服装,再检查每段里的面部、标识和比例。参考能帮助保持一致,但不意味着每个细节都会自动固定,遮挡、大幅度转身与复杂动作尤其需要留意。

提供 3–15 秒、720p/1080p 和多种画幅,适合从一个短场面开始验证。先用少量高质量参考完成主要动作,再添加更多素材,比一次塞入许多风格各异的图片更容易控制。图像之间有矛盾时,应先决定哪张拥有主体外观的优先权。

Use cases and prompting

同一角色走进新的场景

[Image 1] 提供人物身份与发型,[Image 2] 提供浅色外套,[Image 3] 只参考书店空间。人物穿着该外套,沿书架缓慢行走,停下取出一本书。镜头从半身侧面平稳跟随,柔和窗光,书店安静,不增加其他人物和可读招牌。

先检查人物与服装,再调整动作和镜头。

参考图等于首帧吗? 参考图帮助确定主体与风格,生成的新场景不一定照搬某张图的开场构图。

图片越多越好吗? 优先选择清晰且作用明确的素材,避免互相冲突的外观和光线。

系列角色怎样保持连贯? 持续复用身份参考,并逐段检查面部、服装、配件和体型。

API access

API documentation

happyhorse-1.1-r2v

Use the linked documentation for model-specific request parameters and examples.

Authentication

All requests must include Authorization: Bearer <TOKEN> header. Anthropic-formatted endpoints accept the x-api-key header instead.

Generate tokens from the Tokens page; you can scope them to specific models, groups, IPs, and rate-limits.

Rate limits

SupplierRPMTPMRPD
标准按次UnlimitedUnlimitedUnlimited

No restriction

Frequently asked questions about happyhorse-1.1-r2v

What is happyhorse-1.1-r2v?

Compare happyhorse-1.1-r2v API pricing, supported endpoints, capabilities and access options on voguesly.

How do I call happyhorse-1.1-r2v?

Create an API key with access to happyhorse-1.1-r2v, then use the exact model ID and a supported endpoint from the API access section. Request fields depend on the selected endpoint.

How is happyhorse-1.1-r2v priced?

Pricing depends on the selected provider group and the model billing unit. The current input, output, request, or media prices are shown on this page before sign-up.

How should I evaluate happyhorse-1.1-r2v for my project?

Start with the use cases and prompting guidance on this page, then evaluate the model with representative inputs from your project.