API-token calls use a separate workspace USD balance. Only completed jobs are billed; failed or cancelled jobs are not. In-flight jobs finish if funds run out, but new requests return HTTP 402.Source for Billing basis (opens in a new tab)
Processing workflow
Poll GET /jobs/{id} until completed, failed or cancelled. Pending includes backlogged, queued, scheduled, processing, sampling and intermediate-complete. DELETE /jobs/{id} can cancel queued or processing jobs.Source for Processing workflow (opens in a new tab)
Request quotas
Concurrency, backlog and request quotas depend on plan; current guide gives no numerical universal limits. Excess concurrent submissions enter the account backlog.Source for Request quotas (opens in a new tab)
Published catalog marks this tariff variable; no invented flat price or text-question estimate.
Scene transfer
scene_transfer defaults false. When true, scene_image_url is required. Optional scene_prompt; scene_strength 0.5–1, default 0.85; switch_background defaults false. upscaling_activated defaults true.Source for Scene transfer (opens in a new tab)
Endpoint pricing has not been collected. Check the provider for applicable rates.
Data & enterprise terms
General service terms provide broad content-use licenses and make submission visibility depend on plan settings. Exact API retention, residency and a no-training commitment have not been established; enterprise terms may differ.
Caching can reuse earlier input processing. Availability, lifetime and billing depend on the endpoint. A cache hit still generates a new response.
01 / INITIAL INPUTProcess & retain
The system processes eligible input and retains reusable state.
02 / LATER REQUESTCheck available state
Reuse depends on matching input, session state and the cache policy.
03 / CACHE HITReuse & generate
Reusing state can reduce repeated work. Any charges follow the billing rules below.
Krea API
enhance/krea/legacy-enhance
Not verified
No model-specific inference-cache mechanism, TTL or discount established. Reusable styles, moodboards and job records are not prompt caches.
How it works
Not collected
No model-specific inference-cache mechanism, TTL or discount established. Reusable styles, moodboards and job records are not prompt caches.
Minimum reusable input
Not collected
No model-specific inference-cache mechanism, TTL or discount established. Reusable styles, moodboards and job records are not prompt caches.
Lifetime & refresh
Not collected
No model-specific inference-cache mechanism, TTL or discount established. Reusable styles, moodboards and job records are not prompt caches.
How to enable it
Not collected
No model-specific inference-cache mechanism, TTL or discount established. Reusable styles, moodboards and job records are not prompt caches.
Usage fields
Not collected
No model-specific inference-cache mechanism, TTL or discount established. Reusable styles, moodboards and job records are not prompt caches.
Billing rules
Not collected
No model-specific inference-cache mechanism, TTL or discount established. Reusable styles, moodboards and job records are not prompt caches.
Limits & data boundaries
Not collected
No model-specific inference-cache mechanism, TTL or discount established. Reusable styles, moodboards and job records are not prompt caches.
No verified cache rate for this endpoint. An empty rate is not a zero charge.
Caching reviewed 15 Oct 2026
What the measurements say
No benchmark observations have been added for this model. We do not turn a vendor description into a performance score.
Latency and throughput depend on the host, request size, reasoning settings and load. There is no measured speed or global usage figure in this record.
The record behind the model
Why it is included
The provider documents a hosted enhancement model and API contract but does not establish the underlying checkpoint identity or weight-release status. This is represented as a managed component, not an independently verified private foundation model.
