The API policy states inputs and outputs are not used for training. Generated download URLs are retained for about 24 hours according to the API limits guide; the broader no-storage wording must not be interpreted as a verified zero-retention guarantee.
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.
Recraft
recraftv4_1_flash
Not verified
Reusable styles and temporary output URLs do not establish inference-cache support.
How it works
Not collected
Minimum reusable input
Not collected
Lifetime & refresh
Not collected
How to enable it
Not collected
Usage fields
Not collected
Billing rules
Not collected
Limits & data boundaries
Not collected
No verified cache rate for this endpoint. An empty rate is not a zero charge.
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 developer terms explicitly identify Recraft API models as proprietary, reserve underlying model rights and grant limited API access. The reviewed native model catalog ties this exact selector to that service.