tripo3d/tripo-h3.1/multiview-to-3d
Tripo H3.1 Multiview To 3d by Tripo3D - convert 2D images into 3D models with AI. Generate textured 3D assets from single photos for games, AR/VR, e-commerce, and digital content creation.
PNG, JPEG, WebP, or GIF · 20 MiB maximum each
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/runtripo3d/tripo-h3.1/multiview-to-3dInput Schema
1 parameters · 0 required · 1 optional
| Parameter | Type | Required | Description |
|---|---|---|---|
images | string[] | Optional | 2 to 4 image URLs of the same object from different angles. Order: [front, left, back, right]. Front view is required. |
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": "tripo3d/tripo-h3.1/multiview-to-3d",
"images": [
"https://static.sandbase.ai/examples/tripo3d/tripo-h3.1/multiview-to-3d/input_images_0.png",
"https://static.sandbase.ai/examples/tripo3d/tripo-h3.1/multiview-to-3d/input_images_0.png"
],
"prompt": "a beautiful sunset over mountains"
}'
# Step 2: Poll result (replace <id>)
curl https://api.sandbase.ai/v1/run/<id> \
-H "Authorization: Bearer YOUR_API_KEY"API README
Tripo H3.1 Multiview to 3D
Tripo H3.1 Multiview to 3D serves the tripo3d/tripo-h3.1/multiview-to-3d workflow for multiview to 3d work in image production. Teams can place this named operation inside review, asset preparation, and publishing pipelines while keeping the original request attached to every result. Tripo H3.1 Multiview To 3d by Tripo3D - convert 2D images into 3D models with AI. Generate textured 3D assets from single photos for games, AR/VR, e-commerce, and digital content creation. Because tripo3d/tripo-h3.1/multiview-to-3d is a separate catalog entry, evaluations should use this route’s own inputs, output expectations, and billing behavior. The endpoint is especially useful when a project has a defined transformation goal and needs a repeatable request contract instead of an ad-hoc desktop step. This capability boundary is specific to the endpoint named above.
images controls 2 to 4 image URLs of the same object from different angles. Order: [front, left, back, right]. Front view is required. The mandatory portion is no mandatory fields declared by the schema. Tripo H3.1 Multiview to 3D exposes images as its documented request surface. For example, the route documentation includes “https://static.sandbase.ai/examples/tripo3d/tripo-h3.1/multiview-to-3d/input_images_0.png”. Applications can submit that exact shape asynchronously, retain the chosen arguments in job metadata, and collect the resulting media URL for review or publishing.
Highlights
- Structured 3D creation. Tripo H3.1 Multiview to 3D converts the route’s text or visual references into a spatial asset rather than a flat rendered image.
- Geometry reconstruction. The model reasons about visible form and unseen surfaces to produce a coherent object that can be inspected from multiple viewpoints.
- Appearance-aware output. Surface color and material cues are carried into the result so the asset retains the visual character of its source or brief.
- Downstream 3D utility. Generated assets provide a starting point for visualization, concept development, interactive scenes, and further mesh refinement.
Pricing
| Billing option | Price |
|---|---|
| Billing formula | params.textures == "HD" ? 0.30 + (params.detailed_geometry ? 0.20 : 0) + (params.quad_mesh ? 0.05 : 0) : params.textures == "standard" ? 0.20 + (params.detailed_geometry ? 0.20 : 0) + (params.quad_mesh ? 0.05 : 0) : 0.10 + (params.detailed_geometry ? 0.20 : 0) + (params.quad_mesh ? 0.05 : 0) |
| Catalog base price | $0.100000 |
When to Use
| Scenario | Why it fits |
|---|---|
| Choose Tripo H3.1 Multiview to 3D | Use it when the job specifically calls for multiview to 3d and the route’s documented input contract matches assets already available in your workflow. |
| Keep the request reproducible | Use the required inputs explicitly, then record optional choices alongside the prompt for repeatable reruns. |
| Build controlled creative variations | Change one declared control at a time when comparing framing, format, duration, resolution, style, or other route-supported output decisions. |
| Integrate asynchronous delivery | Use this endpoint when an application can submit work, track completion, and collect the returned media URL instead of requiring an immediate inline artifact. |
| Validate before a large batch | Run representative prompts and source assets first, confirm the visual or audio behavior, then lock the successful request shape for scaled production. |
Prompt Guide
Lead with the subject or transformation, then add the composition, environment, style, lighting, motion, voice, or fidelity details relevant to this route. Keep every parameter inside the documented schema; the example below uses only fields declared for tripo3d/tripo-h3.1/multiview-to-3d.
{}
Technical Specs
| Specification | Details |
|---|---|
| Model ID | tripo3d/tripo-h3.1/multiview-to-3d |
| Execution mode | async |
| Task type | image |
images | array · optional |

