Tripo
Tripo H3.1
tripo-h3.1/text-to-3d
Tripo's high-detail 3D generation model, supporting the generation of textured 3D assets from text prompts, a single image, or multiple views, with adjustable polygon count and texture quality and PBR material output, suitable for asset creation such as game props and product visualization
Try tripo-h3.1/text-to-3d
Input
Output
Pricing
tripo-h3.1/text-to-3d per model
+ $0.290 finer geometry
Overview
This is a text-to-3D model generation service where developers can obtain a textured 3D model asset simply by entering a natural language description. Prompts can be up to 1024 characters, support negative prompts to exclude unwanted content, and allow separate configuration of geometry and texture quality, whether to output PBR materials, a triangle face count limit, and multiple random seeds for reproducing results. The generated results are suitable for scenarios such as game prototyping, product visualization, and concept design that require quickly turning text ideas into 3D models, and are aimed at 3D content developers, independent creators, and design teams.
Core Highlights
- Generate 3D assets directly from text — Enter a single description to produce a 3D model with geometry and textures, saving the first step of manual modeling.
- Geometry and texture quality adjustable separately — Geometry quality and texture quality each have Standard and Fine tiers, allowing you to balance detail and output scale according to use.
- PBR material and texture toggles — PBR materials and textures are generated by default, or both can be turned off to keep only a pure geometry mesh, adapting to different downstream pipelines.
- Seed parameters support result reproduction — Random seeds are provided separately for concept image, geometry, and texture, making it easy to repeat or fine-tune generation results under the same settings.
Capabilities
Generate 3D models from text descriptions: Builds 3D geometry from prompts, with prompts up to 1024 characters and optional negative prompts to exclude unwanted elements, suitable for creating concept assets from scratch.
Target triangle face count control: A face count limit parameter can specify the target number of triangles, with a range from 1,000 to 1.5 million (2 million for fine geometry). When not set, the model decides adaptively, making it easy to match downstream rendering requirements.
PBR material and texture output: PBR materials and textures are generated by default; when both texture and PBR are disabled, a pure geometry mesh is output. Texture quality can be Standard or Fine, with the Fine tier producing higher-resolution textures.
Adjustable geometry refinement: Geometry quality can be selected between Standard and Fine. The Fine tier adds denser mesh details, suitable for assets that need close-up presentation or further refinement.
Use Cases
- Rapid prop model production for game prototypes — Designers or independent developers describe a prop's appearance in text, generate a textured 3D model, and import it into an engine for prototype validation and level building.
- Concept asset creation for product visualization — Design teams generate 3D models from product descriptions for early proposal presentation, marketing visual drafts, and internal review.
- 3D concept design iteration — Concept designers batch-generate variants with different prompts and seeds, quickly compare design directions, and select assets to move into the refinement stage.
Limitations and Selection Advice
Prompt length is limited to 1 to 1024 characters; submissions exceeding this cannot be accepted. The face count limit only accepts integers between 1,000 and 1.5 million (2 million for fine geometry); when not set, the model determines the triangle count itself. Texture quality and geometry quality are each a choice of two options, and only one tier can be selected per request. When both texture and PBR are disabled, the output is a pure geometry mesh without surface textures. Seed parameters improve reproducibility, but identical seeds do not guarantee completely identical generation results.
What's new
View changelog →- New model tripo-h3.1/multiview-to-3d is live: Tripo H3.1 Multiview to 3D
- New model tripo-h3.1/text-to-3d is live: Tripo H3.1 Text to 3D
- New model tripo-h3.1/image-to-3d is live: Tripo H3.1 Image to 3D
Frequently asked questions
View all FAQs →-
What is the face count upper limit? Can it reach 2 million?
Yes, the face_limit upper bound is 2 million triangles, but 2 million is only actually supported when geometry_quality is set to detailed; under standard, it is recommended to set it within 1.5 million. If face_limit is not passed, the model adaptively determines the face count.
-
How do I get just a geometry without textures first?
Set both texture and pbr to false. When pbr is true, textures are forcibly generated. If you need textures but not a PBR material, set texture to true and pbr to false.
-
Should high-density geometry have its own separate parameter?
Setting geometry_quality to detailed adds finer mesh detail and is also the prerequisite for the polygon count to reach 2 million; if you need more refined textures, set texture_quality to detailed. Both default to standard, so enable them only as required by the close-up needs of the target asset.
-
How can I reproduce generation results so it's easy to compare different parameters?
Geometry and textures each have their own fixed seed: model_seed controls geometry, texture_seed controls textures, and text-to-3D additionally has image_seed to control the concept image. When comparing parameter settings, first fix the seeds and change only one parameter, so you can tell which item the difference comes from.
Create a generation task
https://api.hiapi.ai/v1/tasks Headers
AuthorizationstringRequiredAccount API key. Required on every request. Example: Bearer YOUR_HIAPI_API_KEY. Get your API key
Content-TypestringOptionalThe request body is always parsed as JSON; when sent, only application/json (optionally with charset) is accepted — any other value returns 415. Example: application/json.
Idempotency-KeystringOptionalIdempotency key, up to 255 bytes. Retries with the same key from the same account create the task only once; replays return the original taskId.
On network timeouts or client retries, the same key creates the task only once — no double charges (scope: the API key's account). Use a business-unique identifier as the key (e.g. "order-42"); replays return the original taskId, and keys expire 24 hours after the first request. See the Unified Async API overview for the full scenario matrix.
Body
modelstringRequiredCurrent fixed value: tripo-h3.1/text-to-3d
routestringOptionalCurrent fixed value: default
inputobjectRequired
Business parameters for tripo-h3.1/text-to-3d and route default — see the parameter table below.
pbrbooleanOptionalDefault: trueWhether to generate PBR materials; takes a boolean value, default is true; when true, texture maps are also output.
promptstringRequiredminLength 1maxLength 1024Description text of the object to generate, for example a small ceramic teapot, used as the input prompt for text-to-3D.
texturebooleanOptionalDefault: trueWhether to generate textures for the model, default is true. Note that when pbr is true, textures are forcibly generated; only when both texture and pbr are set to false is a pure geometry mesh output.
face_limitintegerOptionalmin 1000max 2000000Target triangle count, takes an integer, range 1000–1500000 (up to 2000000 when geometry_quality=detailed); when omitted, the model adaptively determines the face count, and the file is usually large; for web display, around 50000 is recommended.
image_seedintegerOptionalRandom seed for concept image generation, takes an integer, used to reproduce the same concept image result.
model_seedintegerOptionalReproducible random seed for geometry generation, takes an integer, used to stably reproduce the same geometry result.
texture_seedintegerOptionalReproducible random seed for texture generation, takes an integer, used to stably reproduce the same texture result.
negative_promptstringOptionalmaxLength 1024Negative prompt, describing content that should be avoided during generation.
texture_qualitystringOptionalDefault: "standard"Texture quality level, takes a string, default is standard; the detailed level generates higher-resolution textures.
standarddetailedgeometry_qualitystringOptionalDefault: "standard"Geometry quality level, takes a string, default is standard; the detailed level provides finer mesh details.
standarddetailedcallbackobjectOptional
Terminal-state notification config. When omitted, no callback is delivered — poll the task yourself. See the callback note below.
Provide callback.url when creating a task and HiAPI POSTs to your service once the task reaches a terminal state — no polling needed. The callback payload mirrors the task detail structure; signature verification, delivery retries and idempotency are documented on the Unified Async API overview page.
urlstringRequiredRequired when callback is present. A POST is sent to this URL once the task reaches a terminal state; must be a valid http(s) URL.
whenstringOptionalDefault: "final"Only final is supported today — notified on both success and fail.
finalstoragestringOptionalDefault: "temp"Artifact storage tier: temp (default, retained about 7 days) or persistent (long-term, billed by size). Insufficient balance or exceeding the storage cap silently downgrades to temp; the effective tier is shown in the task detail response.
temppersistentRequest examples
# Submit an async task; returns a taskId immediately (no waiting for generation)
curl -X POST "https://api.hiapi.ai/v1/tasks" \
-H "Authorization: Bearer $HIAPI_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "tripo-h3.1/text-to-3d",
"input": {
"pbr": true,
"prompt": "…",
"texture": true,
"texture_quality": "standard",
"geometry_quality": "standard"
}
}' const res = await fetch("https://api.hiapi.ai/v1/tasks", {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.HIAPI_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({
model: "tripo-h3.1/text-to-3d",
input: {
"pbr": true,
"prompt": "…",
"texture": true,
"texture_quality": "standard",
"geometry_quality": "standard"
}
}),
});
const task = await res.json();
// { code: 200, message: "success", data: { taskId } } import os, requests
res = requests.post(
"https://api.hiapi.ai/v1/tasks",
headers={"Authorization": f"Bearer {os.environ['HIAPI_API_KEY']}"},
json={
"model": "tripo-h3.1/text-to-3d",
"input": {
"pbr": True,
"prompt": "…",
"texture": True,
"texture_quality": "standard",
"geometry_quality": "standard"
}
},
)
print(res.json()) # { code, message, data: { taskId } } 200 OK
{
"code": 200,
"message": "success",
"data": {
"taskId": "tk-hiapi-01HZTQ8BX2N3GM3YFK4Z9D7VQR"
}
} 400 Bad Request
{
"code": 400,
"message": "invalid request",
"data": null,
"error_code": "INVALID_REQUEST"
} Get task detail
https://api.hiapi.ai/v1/tasks/:id Response fields
taskIdstringRequiredTask ID, always prefixed with tk-hiapi-.
modelstringRequiredResolved full model name. Tasks submitted with the route parameter return base@route (e.g. gpt-image-2/text-to-image@ext); otherwise identical to the name passed at creation.
routestringOptionalPresent only when the task was submitted with an explicit route parameter; echoes the submitted value.
statusstringRequiredTask status.
queued Queued, not started yet.
handling Being processed.
archiving Processing finished, artifacts being prepared.
success Terminal: completed, artifacts available (output returned).
fail Terminal: failed (error returned).
After submission, check status: success and fail are terminal, everything else is non-terminal. Poll every 1–3 seconds until terminal. On success, download artifacts from output[].url and transfer them before expireAt; pass storage: "persistent" at creation time when long-term retention is needed.
creatednumberRequiredTask creation time (Unix seconds).
completednumberRequiredUnix seconds when the task reached a terminal state; fixed to 0 while not terminal.
outputarrayOptional
Present only when status == success. Artifact list — always an array; a single task may return multiple types at once (e.g. video + first_frame).
Array [ object ]
Array items
urlstringRequiredArtifact URL, directly downloadable.
typestringRequiredCurrent possible values: video, image, audio, first_frame, last_frame, thumbnail; more may be added later.
expireAtnumberRequiredUnix seconds until which the artifact remains accessible; download or transfer before it expires.
errorobjectOptional
Present only when status == fail.
codestringRequiredBusiness error code.
messagestringRequiredError description.
Response examples
Success
{
"code": 200,
"message": "success",
"data": {
"taskId": "tk-hiapi-01HZTQ8BX2N3GM3YFK4Z9D7VQR",
"model": "happyhorse-1-0",
"status": "success",
"created": 1777282033,
"completed": 1777282099,
"output": [
{
"url": "https://cdn.hiapi.ai/tasks/.../video.mp4",
"type": "video",
"expireAt": 1777886899
}
]
}
} Processing (non-terminal)
{
"code": 200,
"message": "success",
"data": {
"taskId": "tk-hiapi-...",
"model": "happyhorse-1-0",
"status": "archiving",
"created": 1777282033,
"completed": 0
}
} Failed
{
"code": 200,
"message": "success",
"data": {
"taskId": "tk-hiapi-...",
"model": "happyhorse-1-0",
"status": "fail",
"created": 1777282033,
"completed": 1777282099,
"error": {
"code": "TASK_FAILED",
"message": "task failed"
}
}
} Articles
View all articles →-
Tutorial
Tripo H3.1 Practical Application Scenarios: 5 High-Value Use Cases and Implementation Essentials
From text-to-3D to multiview reconstruction: choosing the right mode and parameters by business scenario
-
Guide
Tripo H3.1 Getting Started Guide: Choosing Among Three Input Modes, Parameters, and Pricing
A practical guide for developers on 3D generation integration decisions and cost control
-
Comparison
Tripo H3.1 Side-by-Side Comparison and Selection Guide: How to Choose Among Three 3D Generation Paths and How to Save
A developer-oriented trade-off between pricing and capability, starting from input form, geometric refinement, and PBR/texture switches