> ## Documentation Index
> Fetch the complete documentation index at: https://docs.comfy.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Use Krea 2 with Comfy Router

> Call krea/krea-2 through Comfy Router: endpoint, request shape and the response Router returns.

API Reference for `krea/krea-2`, served by Comfy Router from Krea.

## Quick start

Create a key at [platform.comfy.org/profile/api-keys](https://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:** `krea/krea-2`

**Endpoint:** `POST https://api.comfy.org/v2/models/krea/krea-2`

<CodeGroup>
  ```python Python theme={null}
  from comfy_sdk import Comfy

  # Reads COMFY_API_KEY from the environment. Each call sends a fresh
  # Idempotency-Key and waits up to 10 minutes for the finished result.
  with Comfy() as client:
      result = client.models.run(
          "krea/krea-2",
          {
              # Request fields are the provider's own — see Input below.
          },
      )

  print(result)
  ```

  ```typescript TypeScript theme={null}
  import { comfy } from "@comfyorg/sdk";

  // Reads COMFY_API_KEY from the environment. Each call sends a fresh
  // Idempotency-Key and waits up to 10 minutes for the finished result.
  const { data } = await comfy.models.run("krea/krea-2", {
    // Request fields are the provider's own — see Input below.
  });

  console.log(data);
  ```

  ```bash cURL theme={null}
  # Request fields are the provider's own — see Input below.
  curl https://api.comfy.org/v2/models/krea/krea-2 \
    -H "X-API-Key: $COMFY_API_KEY" \
    -H "Idempotency-Key: $(uuidgen)" \
    -H "Content-Type: application/json" \
    -d '{}'
  ```
</CodeGroup>

## Schema

### Input

<Note>
  Router has not published an authored input schema for this model yet: `GET /v2/models/krea/krea-2/openapi.json` returns an open object with `x-comfy-input-schema-authored: false`. Router forwards the body to Krea unchanged, so [Krea's own API reference](https://docs.krea.ai/) is authoritative for the request fields, and nothing is validated server side.
</Note>

### Output

<ResponseField name="completed_at" type="string (date-time)" required>
  Format: `date-time`
</ResponseField>

<ResponseField name="created_at" type="string (date-time)" required>
  Format: `date-time`
</ResponseField>

<ResponseField name="job_id" type="string (uuid)" required>
  Format: `uuid`
</ResponseField>

<ResponseField name="result" type="object" required>
  The finished generation. Not nullable here, unlike on `KreaJob`: a terminal job whose `result` carries no `urls` is answered as a Comfy Router error, so a `200` always carries it.
</ResponseField>

<ResponseField name="result.style_id" type="string">
  Set by loraTraining jobs rather than by a generation; a `200` for these models carries `urls`.
</ResponseField>

<ResponseField name="result.urls" type="string (uri)[]" required>
  The generated images, as downloadable links. At least one, because a `completed` job with an empty `urls` is `success_without_output` and never reaches this document.
</ResponseField>

<ResponseField name="status" type="string" required>
  Always `completed` on this document: it is the only status `classifyKrea` answers `succeeded` on, and Krea's vocabulary is matched without a case fold.

  Possible values: `completed`
</ResponseField>

## Examples

### Output

```json theme={null}
{
  "completed_at": "2027-01-01T00:00:37Z",
  "created_at": "2027-01-01T00:00:00Z",
  "job_id": "7f1c2e84-5b90-4a37-8d61-2c0f9ab4e153",
  "result": {
    "urls": [
      "https://example.invalid/krea/krea-2/generated.png"
    ]
  },
  "status": "completed"
}
```

## 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](/development/comfy-router/headers) page: send an `Idempotency-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.

<CardGroup cols={3}>
  <Card title="Headers" icon="list" href="/development/comfy-router/headers">
    Authentication, idempotency, request IDs, error buckets, retry pacing, spend limits.
  </Card>

  <Card title="Quick Start" icon="rocket" href="/development/comfy-router/quickstart">
    Typed error handling in Python and TypeScript, reading the 422, walking the catalog.
  </Card>

  <Card title="Limitations" icon="triangle-exclamation" href="/development/comfy-router/limitations">
    What Router does not do today, and what to use instead.
  </Card>
</CardGroup>