Skip to main content
Krea 3 is a fast image editing model. It follows plain-language instructions: you say what should change and what should stay the same, and Krea 3 produces the edit in seconds. You can also use it for text-to-image generation.
The Krea 3 API is in early access. Only workspaces in the Krea 3 beta can call it. To request access, contact sales@krea.ai.

Endpoint

The endpoint uses the standard job lifecycle: it returns a job_id, and you poll GET /jobs/{job_id} (or use a webhook) until the job completes. The output image is in result.urls[0].

Quickstart: your first image edit

All requests require a Bearer token. See API Keys & Billing if you don’t have one yet.
1

Upload a reference

POST /assets with your input image. The response returns image_url. You can also pass an external image URL or a base64 data URI directly in image_urls.
2

Create an edit

POST /generate/image/krea/krea-3 with your prompt and reference. Save the job_id from the response.
3

Get the result

Poll GET /jobs/{job_id} until status is completed. The output is in result.urls[0].
Keep your API token on your server. Never ship it in client-side code.

Parameters

With width and height, the output is rounded to the nearest supported aspect ratio and a 1k or 2k canvas. Exact pixel dimensions are not guaranteed.Reusing a seed does not guarantee identical results, because the prompt expansion step can vary between runs.

Thinking modes

Before it generates, Krea 3 interprets your prompt. thinking_mode sets how much planning it does. If you omit thinking_mode, the API uses fast. Both modes support regional_edit.

Regional edits

With regional_edit: true, Krea 3 regenerates only the parts of the image that need to change. Everything else stays exactly as it was, so you can edit the same image again and again without quality loss. Use it for local edits where the rest of the image must stay pixel-exact: recolor or swap an object, add or remove an element, fix a detail, or change the text on a sign. It is the safe way to chain edits on the latest output. Leave it out for global edits that should re-render the whole image: restyling, relighting, changing the season or time of day, reframing, or combining several images into a new scene. Regular edits re-render the whole image, so artifacts can build up when you keep editing the latest output. Regional edits need at least one image in image_urls.

Prompting

Krea 3 is an instruction-following editor. Write the edit in plain language:
  • Lead with the change. Add only the details that help to execute it.
  • Close with one preservation sentence when the rest of the image should stay the same. Do not list everything that should stay the same.
  • When the prompt uses more than one image, refer to each image by what it shows. For example: “Put the sneaker from the second image on the person in the first image.”

Image references

  • Krea 3 uses each reference at its uploaded resolution. A reference larger than 4 MP is resized to 4 MP.
  • Around 1 MP is enough for most edits. Do not upscale a reference before you send it.
  • When fine details matter (small text, logos, fabric, faces in a wide shot), send the highest-resolution version of the image you have.
  • With five or more references in one request, each reference is resized to at most 1536 px on its longest side. For full-detail references, send four or fewer.

Zero Data Retention

Krea 3 supports Zero Data Retention for enterprise workspaces. Send the X-Api-Zero-Data-Retention: 1 header. With Zero Data Retention:
  • Every image in image_urls must be a base64 data URI.
  • thinking_mode can be fast or high.
  • A request can use at most 4 image references.

Pricing

The price per image depends on the output resolution, the thinking mode, and the image references.

Job lifecycle

Job statuses, polling, and results.

Webhooks

Get notified when a job completes instead of polling.