Meshy 5 Retexture
meshy/meshy/v5/retextureMeshy V5 Retexture by Meshy - advanced AI model for 3d-to-3d. Delivers high-quality results with fast inference, suitable for both creative and production workflows.
- Base price
- $0.30USD / run
- Execution
- async
- Model type
- image
- Input fields
- 5
Try the model
Playground
PNG, JPEG, WebP, or GIF · 20 MiB maximum
Your output will appear here
Complete the inputs, then click Run.
Model card
Specifications
Pricing
- Base price
- $0.30 / run
Context & modalities
- Input
- Schema-defined
- Output
- image
Capabilities
- Chat
- Not supported
- Vision
- Not supported
- Reasoning
- Not supported
- Structured output
- Not supported
- Function calling
- Not supported
- Audio input
- Not supported
Access
- Provider
- Meshy
- Model ID
- meshy/meshy/v5/retexture
- Execution
- async
- Base URL
- https://api.sandbase.ai
- API
- Unified Run API
- Endpoint
- /v1/run
API README
Meshy 5 Retexture
Meshy 5 Retexture is a Meshy route built for 3D retexturing. It turns an existing mesh and a visual material brief into updated surface appearance while retaining the supplied geometry, giving creators a focused endpoint instead of forcing one generic workflow across materially different production tasks. The route belongs to a family known for production-oriented 3D creation, editable assets, and fast iteration, so it is best evaluated as a creative system for intentional shots and assets rather than as a one-click novelty generator.
Use this endpoint when the input contract and deliverable match that job exactly. Its documented controls include model_url (URL or base64 data URI of a 3D model to texture. Supports .glb, .gltf, .obj, .fbx, .stl formats. Can be a publicly accessible URL or data URI with MIME type application/octet-stream); enable_pbr (Generate PBR Maps (metallic, roughness, normal) in addition to base color); image_style_url (2D image to guide the texturing process. Supports .jpg, .jpeg, and .png formats. Required if text_style_prompt is not provided. If both are provided, image_style_url takes precedence); text_style_prompt (Describe your desired texture style using text. Maximum 600 characters. Required if image_style_url is not provided). Together, these controls help teams plan predictable iterations, compare outputs under stable settings, and connect generation to game, product, visualization, and spatial-content pipelines without hiding the operational choices that shape the result.
Highlights
- Purpose-built 3d retexturing. The route accepts an existing mesh and a visual material brief and produces updated surface appearance while retaining the supplied geometry; its interface is scoped to that transformation, keeping source assets and creative intent explicit.
- Creative direction. Prompts can describe subject behavior, composition, camera intent, lighting, material, atmosphere, and temporal progression so the result is driven by a shot plan rather than isolated keywords.
- Route-specific control. The request exposes model_url (URL or base64 data URI of a 3D model to texture. Supports .glb, .gltf, .obj, .fbx, .stl formats. Can be a publicly accessible URL or data URI with MIME type application/octet-stream); enable_pbr (Generate PBR Maps (metallic, roughness, normal) in addition to base color); image_style_url (2D image to guide the texturing process. Supports .jpg, .jpeg, and .png formats. Required if text_style_prompt is not provided. If both are provided, image_style_url takes precedence); text_style_prompt (Describe your desired texture style using text. Maximum 600 characters. Required if image_style_url is not provided), allowing the same concept to be tested systematically while preserving a repeatable production setup.
- Pipeline-ready output. The generated 3D asset is returned through the documented asynchronous output contract, which suits review queues, batch iteration, and downstream automation. Artists can inspect topology, UVs, textures, normals, roughness, metallic response, skeletal readiness, polygon budgets, and interchange suitability before approving a build.
Pricing
| Configuration | Price |
|---|---|
| Standard request | $0.300000 |
When to Use
| Scenario | Why this model fits |
|---|---|
| Create the exact route output | Choose it when you need 3D retexturing and already have an existing mesh and a visual material brief. |
| Develop controlled variations | Keep the main brief fixed while changing one documented setting at a time to compare motion, framing, quality, or asset behavior. |
| Build repeatable batches | Use a consistent request shape for catalog, campaign, storyboard, game-asset, or social-content production. |
| Preserve source intent | Prefer this route when the supplied reference material must remain the foundation of updated surface appearance while retaining the supplied geometry. |
| Connect a media pipeline | Use asynchronous results in an automated review, approval, post-production, or asset-management workflow. |
Prompt Guide
Start with the desired result, then describe the source relationship, subject action, composition or camera behavior, lighting, style, and timing. For 3D retexturing, state what must remain stable as clearly as what should change. Use only fields exposed by the schema; the example below is structurally valid for this route.
{
"model_url": "https://static.sandbase.ai/examples/meshy/meshy/v5/retexture/input_model_url_0.glb",
"enable_pbr": false,
"image_style_url": "https://example.com/reference.jpg",
"text_style_prompt": "red and black chest",
"enable_original_uv": true
}
Technical Specs
| Specification | Value |
|---|---|
| Model ID | meshy/meshy/v5/retexture |
| Workflow | 3d retexturing |
| Required inputs | No fields marked required by schema |
model_url | string |
enable_pbr | boolean |
image_style_url | string |
text_style_prompt | string |
enable_original_uv | boolean |
Related Models
Start building
Send your first request
OpenAI-compatible endpoint with unified authentication and usage tracking.
# The quoted heredoc keeps Unicode and shell metacharacters unchanged.
result=$(curl --fail-with-body --silent \
-X POST "https://api.sandbase.ai/v1/run" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
--data-binary @- <<'SANDBASE_JSON'
{
"model": "meshy/meshy/v5/retexture",
"model_url": "https://static.sandbase.ai/examples/meshy/meshy/v5/retexture/input_model_url_0.glb",
"enable_pbr": false,
"text_style_prompt": "red and black chest",
"enable_original_uv": true
}
SANDBASE_JSON
)
run_id=$(printf '%s' "$result" | jq -r .id)
for attempt in $(seq 1 120); do
status=$(printf '%s' "$result" | jq -r .status)
case "$status" in completed|failed|timeout) break ;; esac
sleep 2
result=$(curl --fail-with-body --silent \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
"https://api.sandbase.ai/v1/run/$run_id")
done
status=$(printf '%s' "$result" | jq -r .status)
[ "$status" = completed ] || { echo "Generation ended: $status" >&2; exit 1; }
printf '%s\n' "$result"Choose your model
Compare models
| Model | Type | Default price | Released |
|---|---|---|---|
Meshy 5 RetextureThis model Meshy | Image | $0.30 / run | Oct 18, 2025 |
Meshy | Image | $1.44 / run | Sep 21, 2026 |
Meshy | Image | $1.44 / run | Sep 21, 2026 |
Meshy | Image | $1.44 / run | Sep 21, 2026 |
Questions
FAQ
How do I call Meshy 5 Retexture through SandBase?
Create a SandBase API key, then send requests with the model ID "meshy/meshy/v5/retexture" to Unified Run API (/v1/run) at https://api.sandbase.ai. The request examples on this page show the exact payload.
Do I need a separate Meshy account?
No. One SandBase API key and balance gives you access to Meshy 5 Retexture and the other models in the catalog; you do not need to sign up with Meshy separately.
