meshy/animations, served by Comfy Router from Meshy.
Quick start
Create a key at platform.comfy.org/profile/api-keys and export it asCOMFY_API_KEY. The Python and TypeScript snippets use the Comfy SDKs (pip install comfy-sdk, npm install @comfyorg/sdk); the cURL snippet is the same call over raw HTTP.
Model ID: meshy/animations
Endpoint: POST https://api.comfy.org/v2/models/meshy/animations
Schema
Input
integer
required
The identifier of the animation action to apply.
object
Parameters for post-processing animation files.
integer
default:"30"
The target frame rate. Default is 30. Applicable only when operation_type is change_fps.Possible values:
24, 25, 30, 60string
required
The type of operation to perform.Possible values:
change_fps, fbx2usdz, extract_armaturestring
required
The id of a successfully completed rigging task (from POST /openapi/v1/rigging). The character from this task will be animated.
GET /v2/models/meshy/animations/openapi.json, the same document it validates a call against before the request reaches the provider.
Output
Router does not publish an output schema for this model.Examples
Input
Before you ship
The snippets above are the shortest working call. Three things are the same for every model and are documented once on the Comfy Router headers page: send anIdempotency-Key on every paid call and reuse it when you retry, expect the connection to be held up to Router’s 10 minute deadline, and keep X-Comfy-Request-Id from every response. The SDKs do all three for you; the cURL tab does none of them. On failure, X-Comfy-Error-Type names the bucket, and a 422 means the body failed the model’s schema and was never billed.
Headers
Authentication, idempotency, request IDs, error buckets, retry pacing, spend limits.
Quick Start
Typed error handling in Python and TypeScript, reading the 422, walking the catalog.
Limitations
What Router does not do today, and what to use instead.