Skip to main content
Use recraft/recraftv4_styles_pro with the Comfy Router API. Recraft provides the model; Router gives it the shared authentication and request route below.

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: recraft/recraftv4_styles_pro Endpoint: POST https://api.comfy.org/v2/models/recraft/recraftv4_styles_pro

Schema

Input

Router has not published an authored input schema for this model yet: GET /v2/models/recraft/recraftv4_styles_pro/openapi.json returns an open object with x-comfy-input-schema-authored: false. Router forwards the body to Recraft unchanged, so Recraft’s own API reference is authoritative for the request fields, and nothing is validated server side.

Output

integer
required
Unix timestamp when the generation was created
integer
required
Number of credits used for the generation
object[]
required
Array of generated image information
string
Unique identifier for the generated image
string
URL to access the generated image

Examples

Output

Before you ship

Save one Idempotency-Key for each call and reuse it for retries. Router can hold the connection for up to 10 minutes. The SDKs handle authentication; raw HTTP clients send the headers themselves. Use X-Comfy-Error-Type to classify a failure. 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

Find models, inspect schemas, and retry safely.

Limitations

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