Meshy Print Analyze API Documentation

Meshy Print Analyze API Documentation

Playground

Meshy Printability Analysis checks whether a 3D model is ready to 3D print and reports the issues it finds. Ready-to-use REST inference API, best performance, no coldstarts, affordable pricing.

Features

Meshy Print Analyze examines a 3D model for geometry issues that may affect 3D printing. It reports printability measurements such as watertightness, holes, non-manifold edges, degenerate faces, and volume, with optional wall-thickness evaluation based on the intended printer and print size.

Why Choose This?

• Geometry analysis — Check watertightness, holes, non-manifold edges, degenerate faces, and model volume.
• Wall-thickness evaluation — Evaluate thin areas based on the intended printer and print size.
• Printability report — Review issue counts, measurements, and overall printability status.
• Non-destructive analysis — Inspect the model without modifying its geometry.

Parameters

How to Use

1. Upload a model — Provide the 3D file you want to analyze.
2. Set print options optional — Select a printer type and intended print height when wall-thickness evaluation is needed.
3. Submit — Run the printability analysis.
4. Review the report — Check geometry measurements, issue counts, and wall-thickness results.

Pricing

$0.04 per model.

Printer type and intended print height do not add separate charges.

Best Use Cases

• Pre-print validation — Check a model before sending it to a slicer or printer.
• Topology inspection — Identify holes, non-manifold edges, and degenerate faces.
• Watertightness checks — Verify whether a mesh is closed.
• Wall-thickness review — Find areas that may be too thin for the intended printing process.
• Repair planning — Identify issues before using a mesh repair workflow.

Pro Tips

• Run an analysis before repairing a model to understand which issues need attention.
• Select the intended printer type when wall thickness is important.
• Use intended_print_height_mm when analyzing a GLB model at a specific planned print size.
• Review both issue counts and raw geometry measurements before deciding whether repair is necessary.

Notes

• This operation analyzes the model and does not modify, repair, or resize it.
• The report can include watertightness, volume, holes, non-manifold edges, and degenerate faces.
• Wall-thickness results are included when wall-thickness evaluation is requested.
• intended_print_height_mm is supported for GLB inputs.
• The intended print height is used for analysis and does not resize the source model.
• Use the analysis results to determine whether additional repair or print preparation is needed.

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",
  "printer_type": "fdm"
}
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/print/analyze" \
  -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