models

Alibaba: HappyHorse 1.1

Markdown · JSON

Alibaba: HappyHorse 1.1

Alibaba HappyHorse 1.1 generates short videos with sound from a text brief, one first-frame image or up to nine reference images. Its maker profiles emphasize improved motion, skin detail and cross-clip character consistency. Output is 3–15-second MP4 at 24 fps, with 480p, 720p or 1080p options.

About the model

This description covers the model’s capabilities. Available in Ailoot inputs, outputs and options are listed for the selected method below.

Alibaba HappyHorse 1.1 is a video-generation edition with separately named text-to-video, first-frame image-to-video and reference-to-video profiles. The manufacturer emphasizes improved visual detail, movement, character identity across clips, text stability and audio-visual synchronization. The result is a short video with sound, useful for a product shot, a portrait animation or a small character scene. Select the input mode from what should define the scene: a written concept, an exact opening image or several visual references.

For text-to-video, describe the subject, location, action, framing, camera movement and sound intent. For a short action scene, show a cyclist stopping beside a riverside café while the camera moves gently toward the parked bicycle. Keep the action appropriate to a short clip and describe the final moment. The maker’s current text guide permits up to 5,000 non-Chinese or 2,500 Chinese characters and truncates excess text. Organize the brief so its essential subject and action are explicit rather than buried in repeated adjectives.

First-frame image-to-video uses exactly one image as the opening. Prepare the subject, composition and intended crop in that still, then describe what should move or how the camera should change. The documented image formats are JPEG/JPG, PNG and WEBP, up to 20 MB, with both dimensions at least 300 pixels and an aspect ratio between 1:2.5 and 2.5:1. The output approximates the selected resolution tier while retaining the source image’s proportions. A portrait result therefore starts with a suitable portrait composition rather than an unrelated aspect-ratio instruction.

Reference-to-video accepts one to nine images. The prompt uses [Image 1], [Image 2] and subsequent positions to identify them in the input order. State the role of each reference and name the relevant object or person, so a scene image is not mistaken for a character source. The reference guide accepts JPEG/JPG, PNG or WEBP up to 20 MB, requires the shortest side to be at least 400 pixels and recommends clear references at 720p or higher. Avoid a heavily compressed reference whose identifying detail is already missing.

For a scene with several references, place the person from one image in the room from another while retaining a coat or product supplied by a third. Describe the interaction and camera in the same brief. The 1.1 reference profile highlights stability of subjects, scene style and cinematic motion; inspect the actual result for the intended identity, product markings and spatial placement. Several images give the brief more information, but the review still needs to check which features carried into the video.

The maker lists 480p, 720p and 1080p output for the 1.1 generation modes, with whole-second duration from three to fifteen and MP4 at 24 fps. The API response describes H.264 encoding. Text and reference generation offer shapes including 16:9, 9:16, 1:1, 4:3, 3:4, 4:5, 5:4, 9:21 and 21:9; first-frame generation follows the input image. Choose the shape for the destination and leave room for later captions or layout elements. Inspect the returned video’s actual framing at the intended display size.

The model family’s output includes sound. Give the performance or atmosphere a clear role in the brief, and review any dialogue, effects or background track with the picture. Keep spoken material short enough for the action and pauses rather than compressing a long script into one short shot. Check lip movement, speaker attribution and the actual wording when speech is present. Prompt-language acceptance does not itself define a guaranteed pronunciation or a separate voice-reference input.

The documented maker workflow is asynchronous: a task identifier tracks processing, and a successful result supplies the video location. The result link and task queries are documented with a twenty-four-hour validity period. Retain the completed clip, references and prompt as the revision record. The guides also document seed and watermark controls. A fixed seed can aid comparison, but the maker explicitly says it does not guarantee identical results, so judge the returned artifact rather than assuming one setting fixes every frame.

HappyHorse 1.0 and 1.1 are separate editions. The 1.1 output table adds 480p to the 720p and 1080p options of 1.0, and the 1.1 model pages describe upgrades in detail, motion and consistency. The separately named HappyHorse 1.0 video-edit profile has its own inputs and limits and is not an editing mode to silently assign to 1.1. Review the complete 1.1 clip for identity, motion, framing, text and sound, then make a specific correction while retaining the successful parts of the brief.

Ailoot Ultra · Video POST /v1/videos alibaba/happyhorse-1.1

alibaba/happyhorse-1.1

Alibaba /alibaba/happyhorse-1.1

Overview

Alibaba HappyHorse 1.1 generates short videos with sound from a text brief, one first-frame image or up to nine reference images. Its maker profiles emphasize improved motion, skin detail and cross-clip character consistency. Output is 3–15-second MP4 at 24 fps, with 480p, 720p or 1080p options.

Accepted inputs
Text
Results
Video

Available in Ailoot · inputs & methods

Ailoot Ultra · Video POST /v1/videos
Input types
text
Output types
video
Output format
mp4
Output count
Up to 4 outputs
FieldTypeRequirementValues & limitsDefault
FieldmodelTypestringRequirementRequiredValues & limits
alibaba/happyhorse-1.1
Default—
FieldpromptTypestringRequirementRequiredValues & limits
Minimum length: 1
Maximum bytes: 10,000
Unit: UTF8bytes
Default—
FielddurationTypeintegerRequirementRequiredValues & limits
Minimum: 3
Maximum: 15
Unit: seconds
Default—
FieldresolutionTypestringRequirementRequiredValues & limits
720p
Default—
Fieldaspect_ratioTypestringRequirementRequiredValues & limits
16:9
Default—
Input material combinations

Text to video · Required: prompt

Method parameters and lifecycle
ParameterContract
Parametercontent_typeContractapplication/json
ParameterrequiredContractmodel, prompt, duration, resolution, aspect_ratio
Parameterother_optionsContractfalse
ParameterresolutionContract720p
Parameterprompt_max_bytesContract10000
Parameterduration_integer_rangeContract3, 15
Parameteraspect_ratioContract16:9
Parametergenerate_audioContractmust be omitted (not false); AAC included
Parametermaterial_typesContracttext
Parameteradditional_propertiesContractfalse

Method aliases: /v1/videos/generations, /videos, /videos/generations

Lifecycle: submit_once_poll_original

GET /v1/videos/{request_id}

GET /v1/videos/generations/{request_id}

GET /v1/videos/{request_id}/content

GET /v1/videos/generations/{request_id}/content

Create once and save returned ID.

Poll original status; retain every completed asset and duration.

Pricing

How the final charge is calculated

The displayed rates estimate the cost before generation. The final charge is calculated from the cost recorded for the original generation. Measured output duration and forecast quantities are not the final billable quantity.

Tariff references do not add request options. Supported parameters are listed for the selected method.

Fast mode
Not specified When fast mode is selected
Flex mode
Not specified When flex mode is selected
Maximum reasoning effort
Not specified When maximum reasoning effort uses the default adjustment

Estimated rates for comparison

Prices by configuration

Match each charge to the conditions shown. Use one rate for each set of alternative configurations.

ConfigurationRate scheduleForecast quantityBilling unitBilling conditionsCharge
ConfigurationBase token ratesRate scheduleBase rateForecast quantity—Billing unit—Billing conditions—Charge
Input · Input tokens · Estimate for comparison only — / 1K tokens
Output · Output tokens · Estimate for comparison only — / 1K tokens
Input · Cache read · Estimate for comparison only — / 1K tokens
Input · Cache write · Estimate for comparison only — / 1K tokens
Input · Cache write, 1 hour · Estimate for comparison only — / 1K tokens
ConfigurationVideo priceRate schedule—Forecast quantity—Billing unitper video secondBilling conditionsresolution: 1080pCharge
Output · Video price · Estimate for comparison only $0.2556 per video second
ConfigurationVideo priceRate schedule—Forecast quantity—Billing unitper video secondBilling conditionsresolution: 720pCharge
Output · Video price · Estimate for comparison only $0.1976 per video second
ConfigurationEstimated generation costRate schedule—Forecast quantityone generation estimateBilling unit—Billing conditions—Charge
Output · Estimated generation cost · Estimate for comparison only $0.5928 estimate before generation

This estimate is not an additional charge or a fixed rate for the completed generation.

Ailoot reserves an estimated amount before a request. After the result, it settles the final charge from measured usage. Streaming settlement uses the final usage record. How reservation and settlement work →

Reference tariff details

Model-level reference schedules do not change method selection, quotes or charges. Active charges use the selected Ailoot method rates.

Video configuration price references

Prices by configuration

Match each charge to the conditions shown. Use one rate for each set of alternative configurations.

ConfigurationBilling conditionsCharge
ConfigurationVideo priceBilling conditionsresolution: 720pCharge
Output · Video price $0.1976 per video second

Published price reference for the configuration shown. Final charges follow the actual billed configuration.

ConfigurationVideo priceBilling conditionsresolution: 1080pCharge
Output · Video price $0.2556 per video second

Published price reference for the configuration shown. Final charges follow the actual billed configuration.

Example requests

Ailoot Ultra · Video

curl · exact retained creation
set -eu
: "${AILOOT_API_KEY:?Set your Ailoot API key}"
python3 - <<'PY_REQUEST'
import json,os
from pathlib import Path
p=json.loads('{"model": "alibaba/happyhorse-1.1", "prompt": "A cat in a spacesuit walking on the Moon", "duration": 3, "resolution": "720p", "aspect_ratio": "16:9"}')

Path("request.json").write_text(json.dumps(p,ensure_ascii=False))
PY_REQUEST
curl --fail-with-body --silent --show-error https://api.ailoot.ai/v1/videos \
  -H "Authorization: Bearer $AILOOT_API_KEY" -H 'Content-Type: application/json' \
  --data-binary @request.json -D response-headers.txt -o result.json

Receive and save results

Ailoot Ultra · Video

mp4

  • GET /v1/videos/{request_id}
  • GET /v1/videos/generations/{request_id}
  • GET /v1/videos/{request_id}/content
  • GET /v1/videos/generations/{request_id}/content
Check job status
GET original status
set -eu
: "${AILOOT_API_KEY:?Set your Ailoot API key}"
python3 - <<'PY_STATUS_URL'
import json
from pathlib import Path
from urllib.parse import quote
r=json.loads(Path('result.json').read_text())
if not isinstance(r.get('id'),str) or not r['id']:raise SystemExit('Keep the original response and headers for reconciliation; no returned ID')
Path('status-url.txt').write_text('https://api.ailoot.ai/v1/videos/'+quote(r['id'],safe=''))
PY_STATUS_URL
curl --fail-with-body --silent --show-error "$(cat status-url.txt)" \
  -H "Authorization: Bearer $AILOOT_API_KEY" -D status-headers.txt -o status.json
python3 - <<'PY_RESULT'
import json
from pathlib import Path
r=json.loads(Path('status.json').read_text())
print(json.dumps(r,ensure_ascii=False,indent=2))
print('Keep the complete JSON and response headers; do not resubmit an unknown creation.')
PY_RESULT
Other content reads
Save every completed owned output
set -eu
: "${AILOOT_API_KEY:?Set your Ailoot API key}"
export AILOOT_API_KEY
python3 - <<'PY_ASSETS'
import json,os,subprocess
from pathlib import Path
from urllib.parse import urljoin,urlsplit
r=json.loads(Path('status.json').read_text())
if r.get('status')!='completed':raise SystemExit('Keep the original ID and read its status; never recreate an unknown job')
if not isinstance(r.get('data'),list) or not r['data']:raise SystemExit('Keep the complete original status; no completed outputs supplied')
urls=[]
for i,u in enumerate(r.get('data',[])):
    if not isinstance(u,str):raise SystemExit('Keep the original response; unexpected asset shape')
    urls.append((str(i),u))
for label,path in urls:
    u=urljoin('https://api.ailoot.ai',path);z=urlsplit(u)
    if z.scheme!='https' or z.netloc!='api.ailoot.ai' or z.username or z.password:raise SystemExit('Use the actual returned Ailoot owned content URL')
    target=Path('owned-'+label+'.bin')
    subprocess.run(['curl','--fail-with-body','--silent','--show-error',u,'-H','Authorization: Bearer '+os.environ['AILOOT_API_KEY'],'-D',str(target)+'.headers','-o',str(target)],check=True)
print('All returned owned URLs saved; complete metadata, timing and usage remain in the JSON.')
PY_ASSETS
Keep all completed results

Save every completed video or returned file; retrieve every actual returned asset URL.

Completed data[] contains all owned signed content URLs. Fetch each returned URL, or use the content endpoint with index set to an actual output index. A failed original job may return charge_pending_check; check that original job rather than creating it again.

If the original response needs checking

Read existing original job; never resubmit unknown send.

Maximum outputs: 4.

Response fields
FieldTypeMeaning
FieldidTypestringMeaning—
FieldobjectTypestringMeaning—
FieldmodelTypestringMeaning—
FieldstatusTypestringMeaning—
Fielddata[]Typesigned content URLMeaning—
Fieldcharge_pending_checkTypebooleanMeaning—
Fielderror.codeTypestringMeaning—
Fielderror.messageTypestringMeaning—
Fieldoperation_idTypestringMeaningHTTP503 result_pending_check original status/content response: same original public video ID as id.
Fielderror.typeTypestringMeaningserver_error on HTTP503 result_pending_check.
Errors and next steps
ResponseConditionNext step
Response400 · invalid_request_errorConditionReading the raw request body fails before parsing the video profileNext stepPreserve the returned response and correct the unreadable request body.
Response422 · price_unavailableConditionParsing the exact video profile fails, or the complete parsed profile has no ready exact price cardNext stepPreserve the response; use the complete exact admitted profile and its published card. This branch runs before a provider send.
Response409 · video_not_readyConditionOriginal result content is not yet availableNext stepPoll the original returned ID and respect Retry-After.
Responseserver_errorConditionThe returned response says the operation or result requires a checkNext stepKeep the original returned operation/task ID, request headers and response; continue supported reads of that original operation. Do not resubmit the creation request.
Response503 · result_pending_checkConditionGET original status/content: task is not published, original job is not failed/cancelled/expired, and local state is unknown or original job status is completed.Next stepKeep original id and operation_id (same public video ID), response and headers; read only the original status/content. Never submit a new generation request.

Aliases

Model aliases

Ailoot Ultra alibaba/happyhorse-1.1

Method path aliases

/v1/videos/generations, /videos, /videos/generations

Related caller IDs

alibaba/happyhorse-1.1

FAQ · Alibaba: HappyHorse 1.1
What inputs and results are available?

POST /v1/videos · alibaba/happyhorse-1.1: text → video

Which fields does the request use?

POST /v1/videos · alibaba/happyhorse-1.1: model, prompt, duration, resolution, aspect_ratio

What limits apply?

POST /v1/videos · alibaba/happyhorse-1.1: duration.minimum: 3; duration.maximum: 15

More details

Connect Ailoot to Claude Code, OpenCode, Hermes or your own app.

The company and its project portfolio

The company and its project portfolio: millions of customers; monthly sales in the billions.

Buy tokens at a discount.

Subscription discounts for regular use. Promo codes offer up to 50% off token purchases.

Subscription
Choose a discounted plan for your regular requests.
Promo code: up to 50% off
Enter your code at checkout. The price updates to reflect the current promotion.
Spending in your history
The model, tokens and amount are recorded for each request.

Choose a subscription · View model prices

Connect the API to a product you sell.

Use Ailoot in SaaS, apps and bots under its official service offer and licence agreement. Request a reseller licence for resale.

Commercial application
Add text, image, video and audio generation to paid features in your service.
Reseller licence
Send a description of your project and how you provide access. Request written terms for use and resale.
Documents on the website
The service offer, licence agreement and data processing policy are available before you connect.

Request a reseller licence · Service offer and licence agreement