兔子API
provider
HappyHorse
Direct answerDirect access uses a region- and workspace-matched Alibaba Cloud key, endpoint, and required asynchronous header; this gateway's /v1/videos uses its own token. Task IDs and video URLs last only 24 hours and must be retrieved promptly.
Updated · Reviewed
Verifiable ownership boundary
All currently verifiable HappyHorse material comes from Alibaba Cloud Model Studio: the catalog lists model IDs, the API reference documents invocation, and the asynchronous guide covers query and cancellation. No independent first-party developer source was found, so this page treats it as an Alibaba-distributed capability and makes no claim about a separate vendor, weight provenance, or long-term SLA.
Direct access versus this gateway
Direct access requires the model, workspace endpoint, and Model Studio API key to belong to the same region; Beijing, Singapore, and other regions use different hosts. HTTP task creation requires X-DashScope-Async: enable and a Bearer API key. This gateway exposes only the adapted /v1/videos with its own Bearer token; Alibaba keys, provider task paths, and gateway credentials are not interchangeable.
Asynchronous jobs and temporary results
Creation returns task_id plus request_id for troubleshooting, not a video. States include PENDING, RUNNING, SUCCEEDED, FAILED, CANCELED, and UNKNOWN. The official page gives both task-query validity and successful video URLs a 24-hour lifetime. Poll with bounds and stream successful media immediately into controlled storage.
Errors, cost, and idempotency
A mismatched region, key, endpoint, or model fails, and omitting the asynchronous header also produces an error. Store an idempotency record for each business request so timeouts do not create duplicate billed jobs. Cap concurrency, polling, duration, and retries, and retain request_id, code, and message. Use live Alibaba Cloud pages for model IDs, region, and price.
Rights, moderation, and compliance
Prompts, reference images, input video, people, trademarks, and music require appropriate rights, and platform moderation must be handled. Distribution documentation does not establish an independent author, training-data provenance, or weight license; workloads requiring those claims or a long-term SLA need additional official evidence.
Reviewed provider catalog
Latest models by capability
These are provider-catalog models, not a promise of availability on this site. Confirm callable IDs, endpoints, and pricing in the model marketplace.
Video generation and editing
-
happyhorse-1.1-t2vStableAn Alibaba Cloud Model Studio text-to-video model with synchronized audio, 1080p, and 3–15 second output.
-
happyhorse-1.1-i2vStableAn Alibaba Cloud Model Studio first-frame image-to-video model with synchronized audio.
-
happyhorse-1.1-r2vStableAn Alibaba Cloud Model Studio reference-to-video model emphasizing subject consistency.
Use cases
- Text-to-video
- Image-to-video
- Asynchronous content generation
API protocols
/v1/videos
FAQ
Is HappyHorse a separately verified model vendor?
That cannot currently be claimed. This page found Alibaba Cloud Model Studio catalog, invocation, and asynchronous-task material but no independent first-party developer source, so it describes HappyHorse only as an Alibaba-distributed model capability.
How does direct HappyHorse authentication differ from this gateway?
Direct access uses a Model Studio key and workspace endpoint from the model's region and sends X-DashScope-Async: enable when creating an HTTP task. This gateway's /v1/videos uses its own Bearer token and does not accept an Alibaba Cloud key directly.
Why is no video available immediately after HappyHorse returns task_id?
HTTP supports asynchronous jobs only, and task_id means accepted rather than complete. Query PENDING, RUNNING, SUCCEEDED, FAILED, CANCELED, or UNKNOWN; do not create a duplicate after a timeout, and retain request_id for troubleshooting.
Can a HappyHorse task_id and video_url be retained indefinitely?
No. The current Alibaba Cloud page says the task ID query window and successful video URL are both 24 hours. An expired task can become UNKNOWN and the URL is purged, so validate and stream successful output promptly into your own object storage.