tencent/hunyuan-motion
Hunyuan Motion by Tencent - generate 3D models from text descriptions with AI. Create detailed 3D assets from natural language for games, visualization, and digital production.
Example output — click Run to generate your own
Send your first request
OpenAI-compatible endpoint with unified authentication and usage tracking.
https://api.sandbase.ai/v1/runtencent/hunyuan-motionInput Schema
3 parameters · 1 required · 2 optional
| Parameter | Type | Required | Description |
|---|---|---|---|
prompt | string | Required | Text prompt describing the motion to generate. |
duration | integer | Optional | Motion duration in seconds (0.5-12.0). · Min: 0.5 · Max: 12 · Default: 5 |
output_format | string | Optional | Output format: 'fbx' for animation files, 'dict' for raw JSON. · Options: fbx, dict · Default: "fbx" fbxdict |
Output Schema
| Field | Type | Description |
|---|---|---|
id | string | Unique identifier for the generation task |
status | string | Task status: pending, running, completed, failed, timeout |
model | string | Model used for the generation |
outputs | array | Array of output items |
outputs[].url | string | URL of the generated artifact |
outputs[].content_type | string | MIME type (e.g. image/png, video/mp4) |
error | object | null | Error details if failed, null on success |
error.type | string | Machine-readable error type code |
error.message | string | Human-readable error description |
Async Workflow
This model uses asynchronous execution. Submit a request and poll for the result.
- Submit — POST to /v1/run, receive an
id - Poll — GET /v1/run/{id} until status is
completed,failed, ortimeout - Retrieve — Read
outputsfrom the completed response
Code Examples
Ready-to-run snippets
# Step 1: Submit
curl -X POST https://api.sandbase.ai/v1/run \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_API_KEY" \
-d '{
"model": "tencent/hunyuan-motion",
"prompt": "A person is running then takes a big leap.",
"duration": 5,
"output_format": "fbx"
}'
# Step 2: Poll result (replace <id>)
curl https://api.sandbase.ai/v1/run/<id> \
-H "Authorization: Bearer YOUR_API_KEY"API README
Hunyuan Motion
Hunyuan Motion occupies a clearly bounded position in a image production pipeline under the route tencent/hunyuan-motion. It is best evaluated as a named workflow endpoint rather than as a generic substitute for neighboring versions: planners can assign the route to a specific brief, record the chosen revision, and keep approval history tied to one predictable integration surface from intake through delivery.
A practical rollout of Hunyuan Motion should begin with source-readiness checks, ownership of the submitted material, an agreed budget, and a written definition of the final hunyuan motion deliverable. Before automation is enabled, the acceptance pass should verify that the returned asset opens correctly, fits the intended downstream toolchain, satisfies the project’s review criteria, and can be reproduced from the stored request and route identity tencent/hunyuan-motion.
Highlights
- Distinct output behavior. For Hunyuan Motion, for Hunyuan Motion, describe the action that the generated 3D motion should perform In Hunyuan Motion, this capability is applied through the exact tencent/hunyuan-motion workflow with prompt as a relevant request control; the prompt control exposes the corresponding choice in this route; the prompt control exposes the corresponding choice in this route.
- Creative control. For Hunyuan Motion, for Hunyuan Motion, set a clip length between 0.5 and 12 seconds In Hunyuan Motion, this capability is applied through the exact tencent/hunyuan-motion workflow with duration as a relevant request control; the duration control exposes the corresponding choice in this route; the duration control exposes the corresponding choice in this route.
- Workflow fit. For Hunyuan Motion, for Hunyuan Motion, select FBX for a packaged motion asset In Hunyuan Motion, this capability is applied through the exact tencent/hunyuan-motion workflow with output format as a relevant request control; the output format control exposes the corresponding choice in this route; the output format control exposes the corresponding choice in this route.
- Production detail. For Hunyuan Motion, for Hunyuan Motion, select dict when JSON motion data is the desired result In Hunyuan Motion, this capability is applied through the exact tencent/hunyuan-motion workflow.
Pricing
| Configuration | Price |
|---|---|
| Per request | $0.08 |
When to Use
| Scenario | Why this model fits |
|---|---|
| Choose Hunyuan Motion | Use it when the required deliverable is specifically the image result documented for tencent/hunyuan-motion. |
| Match the source material | Select this route when your inputs naturally map to prompt, duration, output_format. |
| Use its distinguishing capability | For Hunyuan Motion, describe the action that the generated 3D motion should perform In Hunyuan Motion, this capability is applied through the exact tencent/hunyuan-motion workflow with prompt as a relevant request control; the prompt control exposes the corresponding choice in this route |
| Plan repeatable production | For Hunyuan Motion, set a clip length between 0.5 and 12 seconds In Hunyuan Motion, this capability is applied through the exact tencent/hunyuan-motion workflow with duration as a relevant request control; the duration control exposes the corresponding choice in this route |
| Confirm cost and delivery | Use the pricing combinations below and the output contract above when budgeting or automating Hunyuan Motion jobs. |
Prompt Guide
Build the request around the exact tencent/hunyuan-motion schema. Start with required fields, then add only the controls needed for the intended output; keep URLs reachable and enum values exactly as shown in Technical Specs.
{
"prompt": "A person is running then takes a big leap.",
"duration": 5,
"output_format": "fbx"
}
Technical Specs
| Specification | Value |
|---|---|
| Model ID | tencent/hunyuan-motion |
| Execution mode | async |
| Required inputs | prompt |
| Request fields | prompt (string, required); duration (integer, optional, min 0.5, max 12); output_format (string, optional, options: fbx / dict) |
| Output | url (string); content_type (string) |