Skip to main content
API Reference for meshy/animations, served by Comfy Router from Meshy.

Quick start

Create a key at platform.comfy.org/profile/api-keys and export it as COMFY_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, 60
string
required
The type of operation to perform.Possible values: change_fps, fbx2usdz, extract_armature
string
required
The id of a successfully completed rigging task (from POST /openapi/v1/rigging). The character from this task will be animated.
Generated from the schema Router serves at 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 SDKs create an Idempotency-Key and reuse it for automatic retries. For manual retries, reuse the original key. Router can hold the connection for up to 10 minutes. When a request fails, Router sends an X-Comfy-Error-Type response header explaining why. A 422 means Router rejected the input before calling the provider. Download generated assets promptly because result URLs can expire.

Headers

Authentication, idempotency, request IDs, error buckets, retry pacing, spend limits.

Using the Router API

Model discovery, validation errors, retries, and billing.

Limitations

What Router does not do today, and what to use instead.