Meshy Rigging API Documentation

Meshy Rigging API Documentation

Playground

Meshy Rigging adds a skeleton to a humanoid or four-legged character model. Ready-to-use REST inference API, best performance, no coldstarts, affordable pricing.

Features

Meshy Rigging adds a skeleton to an existing 3D character model, preparing it for animation workflows. Choose a biped or quadruped skeleton and set the character’s approximate height for more accurate rigging.

Why Choose This?

• Automatic character rigging — Add a skeleton and skinning to an existing character model.
• Biped and quadruped support — Choose the skeleton type that matches the character.
• Height control — Set the character’s approximate real-world height.
• Animation-ready output — Prepare characters for subsequent animation workflows.

Parameters

How to Use

1. Upload a character model — Provide the source 3D file.
2. Choose the skeleton type — Select biped or quadruped.
3. Set the character height optional — Adjust height_meters when needed.
4. Submit — Generate and retrieve the rigged model.

Pricing

$0.20 per model.

Skeleton type and character height do not add separate charges.

Best Use Cases

• Game characters — Prepare characters for animation in real-time projects.
• Character prototyping — Quickly add a skeleton to newly generated 3D characters.
• Animation preparation — Rig characters before applying preset animations.
• 3D production workflows — Prepare character assets for downstream editing and motion work.

Pro Tips

• Use a character with clearly defined limbs and body structure.
• A neutral A-pose or T-pose generally provides better rigging results.
• Choose animation_type to match the character’s body structure.
• Set an approximate real-world height for more accurate rigging.
• Reduce very dense meshes before rigging when necessary.

Notes

• model is required.
• animation_type defaults to biped.
• height_meters defaults to 1.7.
• The input model supports up to 380,000 triangles.
• Models above the triangle limit should be simplified or remeshed before rigging.
• Rigging adds a skeleton to the character but does not apply a specific animation.
• Use the Meshy Animation workflow to add motion after rigging.

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",
  "animation_type": "biped",
  "height_meters": 1.7
}
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/rigging" \
  -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