Skip to main content
API Reference for typesafe/jev-1.13.0, served by Comfy Router from Typesafe. Input: Text, Image · Output: Text

Quick start

Create a key in your Comfy workspace and export it as COMFY_API_KEY. The Python and TypeScript snippets use the Comfy SDKs (pip install comfy-sdk and npm install @comfyorg/sdk); the cURL snippet is the same call over raw HTTP. Model ID: typesafe/jev-1.13.0 Endpoint: POST https://api.comfy.org/v2/models/typesafe/jev-1.13.0
The same body, sent to POST https://api.comfy.org/v2/models/typesafe/jev-1.13.0/requests. Router answers 201 with a request_id as soon as the run is admitted, and the result is collected once it is ready, from this process or another one. Queued delivery walks through status, cancellation and collection.

Schema

Input

object
The images in the request, keyed by a reference string. Every reference must appear somewhere in state, instructions or criteria. Each image is a still PNG or JPEG of 280 to 1568 pixels per side and at most 16 MiB after decoding; TypeSafe refuses a call over 32 MiB in total.
string
The pinned Jev version. Optional: Router fills it from the model id in the path. The jev-latest and jev-preview aliases are not accepted.
object
required
The questions to answer, keyed by an id you choose. The answer to each is returned under the same id.
object
required
The content to evaluate: a string, or structured data (an object or array) up to 64 levels deep. An asset reference anywhere in it is replaced by that image.
Generated from the schema Router serves at GET /v2/models/typesafe/jev-1.13.0/openapi.json, the same document it validates a call against before the request reaches the provider.

Output

object
required
One answer per question, keyed by the question ids you sent.
string
required
The Jev version that answered, such as jev-1.14.0.
object
Token usage for the request.
integer
Input tokens, including every image in the request.
integer
Output tokens.

Examples

Input

Output

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, and a 413 means the request body was larger than Router accepts. Download generated assets promptly because result URLs can expire. Any size limit named in a field description above is the provider’s own bound on that field, quoted from the provider’s specification. Router applies a separate cap to the whole request body, which base64-encoded media counts against: see request body size. This page documents one partner model called through Comfy Router. The same comfy-sdk / @comfyorg/sdk package also ships a second client, for running a whole ComfyUI workflow graph on Comfy Cloud: Comfy(api_key=...) / new Comfy({ apiKey }), with client.workflows, client.assets and client.jobs. See Comfy SDKs.

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.