Meshy Remesh API Documentation

Meshy Remesh API Documentation

Playground

Meshy Remesh rebuilds a 3D model at a target polycount, as triangles or quads. Ready-to-use REST inference API, best performance, no coldstarts, affordable pricing.

Features

Meshy Remesh rebuilds an existing 3D model with cleaner topology and a target polygon count. Choose triangle or quad topology, control mesh density, and optionally adjust the model’s scale and origin.

Why Choose This?

• Topology rebuilding — Rebuild irregular or overly dense meshes for downstream workflows.
• Triangle or quad output — Choose the topology that fits your editing or production needs.
• Polygon control — Set a target face count from 100 to 300000.
• Proportional scaling — Optionally estimate an appropriate real-world scale.
• Origin control — Position the model origin at the bottom or center.

Parameters

How to Use

1. Upload a model — Provide the source 3D file.
2. Choose topology — Select triangle or quad.
3. Set polygon count — Choose the target number of faces.
4. Configure scale optional — Enable auto_size when estimated real-world scaling is needed.
5. Choose origin optional — Place the origin at the bottom or center.
6. Submit — Generate and retrieve the remeshed model.

Pricing

$0.20 per model.

Topology, target polygon count, automatic sizing, and origin placement do not add separate charges.

Best Use Cases

• Game assets — Reduce or standardize polygon counts for real-time workflows.
• 3D editing — Create cleaner topology before further modeling or sculpting.
• UV preparation — Remesh dense or irregular geometry before UV unwrapping.
• Rigging preparation — Create more manageable topology before character rigging.
• Asset optimization — Reduce mesh complexity for downstream applications.

Pro Tips

• Use a lower target_polycount when performance and file size are more important than fine detail.
• Increase the target count when the source contains small or complex features.
• Use triangle for general-purpose optimized meshes.
• Use quad when quad-dominant topology is preferred for downstream editing.
• Review the remeshed result before continuing with UV, texture, or rigging workflows.

Notes

• topology defaults to triangle.
• target_polycount supports values from 100 to 300000 and defaults to 30000.
• The requested polygon count is a target and may not exactly match the final result.
• Lower polygon counts may reduce small geometric details.
• auto_size estimates the object’s real-world height and rescales the model accordingly.
• origin_at supports bottom and center.
• Meshy now recommends using the dedicated Resize workflow for new integrations that need automatic sizing or origin adjustment.

Authentication

For authentication details, please refer to the Authentication Guide.

API Endpoints

Submit Task & Query Result

set -euo pipefail

export WAVESPEED_API_KEY="your-api-key"

REQUEST_BODY=$(cat <<'JSON'
{
  "model": "example",
  "topology": "triangle",
  "target_polycount": 30000,
  "auto_size": false,
  "origin_at": "bottom"
}
JSON
)

# 1. Submit the prediction once. Never retry this request automatically:
# a retry after an unclear failure can create a second, billed task.
CHECK='The task may already exist. Check History or the predictions list before submitting again.'
if ! SUBMIT_RESPONSE=$(curl --silent --show-error --fail-with-body \
  --connect-timeout 10 --max-time 60 \
  -X POST "https://api.wavespeed.ai/api/v3/meshy/remesh" \
  -H "Authorization: Bearer ${WAVESPEED_API_KEY}" \
  -H "Content-Type: application/json" \
  -d "${REQUEST_BODY}"); then
  printf 'Submit failed. %s\n' "${CHECK}" >&2
  exit 1
fi

TASK=$(printf '%s' "${SUBMIT_RESPONSE}" | jq 'if type == "object" and has("data") then .data else . end')
PREDICTION_ID=$(printf '%s' "${TASK}" | jq -r '.id // empty')
if [ -z "${PREDICTION_ID}" ]; then
  printf 'Submission response did not contain a prediction id. %s\n' "${CHECK}" >&2
  exit 1
fi
RESULT_URL="https://api.wavespeed.ai/api/v3/predictions/${PREDICTION_ID}/result"

# 2. Poll until the prediction reaches a final status.
BODY_FILE=$(mktemp)
trap 'rm -f "${BODY_FILE}"' EXIT
while true; do
  # Transient errors (429, 5xx) are retried, honoring Retry-After.
  HTTP_CODE=$(curl --silent --show-error --fail-with-body \
    --connect-timeout 10 --max-time 60 --retry 5 --retry-delay 2 \
    --output "${BODY_FILE}" --write-out '%{http_code}' \
    "${RESULT_URL}" \
    -H "Authorization: Bearer ${WAVESPEED_API_KEY}" || true)
  case "${HTTP_CODE}" in
    2??) ;;
    000|429|5??)  # dropped connection or temporary error: keep polling
      printf 'Task %s: HTTP %s, polling again in 10s\n' "${PREDICTION_ID}" "${HTTP_CODE}" >&2
      sleep 10; continue ;;
    *) printf 'Task %s: HTTP %s\n' "${PREDICTION_ID}" "${HTTP_CODE}" >&2
      cat "${BODY_FILE}" >&2; exit 1 ;;
  esac
  RESULT=$(jq 'if type == "object" and has("data") then .data else . end' "${BODY_FILE}")
  STATUS=$(printf '%s' "${RESULT}" | jq -r '.status // empty')

  case "${STATUS}" in
    completed) printf '%s\n' "${RESULT}" | jq '.outputs'; break ;;
    failed|cancelled|timeout|deleted)
      printf 'Task %s ended with status %s\n' "${PREDICTION_ID}" "${STATUS}" >&2
      printf '%s\n' "${RESULT}" | jq . >&2; exit 1 ;;
    *) sleep 2 ;;
  esac
done

Parameters

Task Submission Parameters

Request Parameters

Every model also accepts the global request options enable_sync_mode and enable_base64_output; see their pages for details.

Response Parameters

Result Request Parameters

Result Response Parameters