Recraft V4.1 Utility Pro is the higher-resolution raster variant of the Utility branch within Recraft V4.1. The manufacturer distinguishes Utility’s straightforward presentation from the main V4.1 model’s more expressive choices of angle, lighting and composition. Utility favours simple scenes, flat lighting and front-facing subjects. It is therefore suited to product-listing visuals, mockups and other work where the object should be easy to read and a calm composition serves the task.
The exact model code is recraftv4_1_utility_pro. Its producer reference lists 2K raster output with finer detail, in lossless WebP or PNG. The size table gives 2048 × 2048 pixels for square images and 2432 × 1792 for 4:3, with other supported aspect ratios using their own dimensions. This separates Utility Pro from standard Utility’s 1K output. It does not turn the image into an editable vector file; a Vector edition supplies SVG for that purpose.
Begin with a brief that names the object, material, viewing angle, background and the few details that must be visible. For a product listing, request a front-facing ceramic storage jar on a light neutral surface, even illumination, a closed lid and clear space around the silhouette. If the scene must remain straightforward, say so explicitly rather than relying on the Utility name to encode all presentation choices. For a series of listing images, keep framing and background requirements consistent while changing the product description.
The V4.1 generation reference supports prompts up to 10,000 characters, preferred-colour and background-colour controls, a random seed and one to six outputs. A compatible saved style or optional reference images can guide appearance; the dedicated V4 Styles family is the separate line where a style is always mandatory. For optional references, use clear assets whose visual direction agrees. Exact colour reproduction from a reference is not guaranteed, so a brand-colour requirement still needs an explicit brief and a check of the output. For reference-style generation, use one to ten PNG, JPG or WebP images, no more than 64 MB in total and under 20 MB each. Each reference needs a shortest side of at least 256 pixels, a longest side of no more than 4,096 pixels and a resolution of no more than 16 megapixels. Use either these references or a compatible saved style, rather than both. For reference-style generation, flexible matching allows a looser interpretation, while precise matching follows the rendering, palette, composition and lighting more closely.
Recraft also documents image-to-image for the V4.1 line, combining an existing image with a prompt and strength from 0 to 1. A lower strength stays closer to the source and a higher value permits a larger change. This is useful when the starting composition or subject should inform a new version. It does not accept V4.1 custom style controls in the same transformation operation. Its producer image input limits are under 20 MB, up to 16 MP and sides between 256 and 4096 pixels.
Utility Pro shares the V4.1 restrictions on negative_prompt, curated style names, text_layout, artistic_level and no_text controls. Give a positive description of the intended scene and reserve precise lettering or layout work for an appropriate finishing step when needed. Review a product visual for the supplied material, shape and necessary details before treating it as a faithful listing asset. The useful result is a larger raster composition prepared for a clear product or mockup brief, while the exact product facts remain those supplied in the task.
", "aboutText": "Recraft V4.1 Utility Pro is the higher-resolution raster variant of the Utility branch within Recraft V4.1. The manufacturer distinguishes Utility’s straightforward presentation from the main V4.1 model’s more expressive choices of angle, lighting and composition. Utility favours simple scenes, flat lighting and front-facing subjects. It is therefore suited to product-listing visuals, mockups and other work where the object should be easy to read and a calm composition serves the task.\n\nThe exact model code is recraftv4_1_utility_pro. Its producer reference lists 2K raster output with finer detail, in lossless WebP or PNG. The size table gives 2048 × 2048 pixels for square images and 2432 × 1792 for 4:3, with other supported aspect ratios using their own dimensions. This separates Utility Pro from standard Utility’s 1K output. It does not turn the image into an editable vector file; a Vector edition supplies SVG for that purpose.\n\nBegin with a brief that names the object, material, viewing angle, background and the few details that must be visible. For a product listing, request a front-facing ceramic storage jar on a light neutral surface, even illumination, a closed lid and clear space around the silhouette. If the scene must remain straightforward, say so explicitly rather than relying on the Utility name to encode all presentation choices. For a series of listing images, keep framing and background requirements consistent while changing the product description.\n\nThe V4.1 generation reference supports prompts up to 10,000 characters, preferred-colour and background-colour controls, a random seed and one to six outputs. A compatible saved style or optional reference images can guide appearance; the dedicated V4 Styles family is the separate line where a style is always mandatory. For optional references, use clear assets whose visual direction agrees. Exact colour reproduction from a reference is not guaranteed, so a brand-colour requirement still needs an explicit brief and a check of the output. For reference-style generation, use one to ten PNG, JPG or WebP images, no more than 64 MB in total and under 20 MB each. Each reference needs a shortest side of at least 256 pixels, a longest side of no more than 4,096 pixels and a resolution of no more than 16 megapixels. Use either these references or a compatible saved style, rather than both. For reference-style generation, flexible matching allows a looser interpretation, while precise matching follows the rendering, palette, composition and lighting more closely.\n\nRecraft also documents image-to-image for the V4.1 line, combining an existing image with a prompt and strength from 0 to 1. A lower strength stays closer to the source and a higher value permits a larger change. This is useful when the starting composition or subject should inform a new version. It does not accept V4.1 custom style controls in the same transformation operation. Its producer image input limits are under 20 MB, up to 16 MP and sides between 256 and 4096 pixels.\n\nUtility Pro shares the V4.1 restrictions on negative_prompt, curated style names, text_layout, artistic_level and no_text controls. Give a positive description of the intended scene and reserve precise lettering or layout work for an appropriate finishing step when needed. Review a product visual for the supplied material, shape and necessary details before treating it as a faithful listing asset. The useful result is a larger raster composition prepared for a clear product or mockup brief, while the exact product facts remain those supplied in the task.", "editorialOverlay": { "copy_fields": null, "copy_sha256": null, "copy_source": null, "html_sha256": "28783ae759602f39f6908eec360a3bf926d1248eb68a1c7eefbfb7759386e50f", "module_sha256": "ee9dc1c50b1e6a8fb7fa062030fcb4646b9aaaeb08be513b723a5a92a7290f06", "raw_model_unchanged": true, "schema": "ailoot-native-model-editorial-v1" }, "locale": "en", "methods": [ { "html": "recraft/recraft-v4.1-utility-proRecraft V4.1 Utility Pro generates 2K raster images with a focus on simple, predictable scenes, flat lighting and front-facing composition. It suits detailed product shots and mockups that need a clear presentation rather than an expressive art direction.
This description covers the model’s capabilities. Available in Ailoot inputs, outputs and options are listed for the selected method below.
Recraft V4.1 Utility Pro is the higher-resolution raster variant of the Utility branch within Recraft V4.1. The manufacturer distinguishes Utility’s straightforward presentation from the main V4.1 model’s more expressive choices of angle, lighting and composition. Utility favours simple scenes, flat lighting and front-facing subjects. It is therefore suited to product-listing visuals, mockups and other work where the object should be easy to read and a calm composition serves the task.
The exact model code is recraftv4_1_utility_pro. Its producer reference lists 2K raster output with finer detail, in lossless WebP or PNG. The size table gives 2048 × 2048 pixels for square images and 2432 × 1792 for 4:3, with other supported aspect ratios using their own dimensions. This separates Utility Pro from standard Utility’s 1K output. It does not turn the image into an editable vector file; a Vector edition supplies SVG for that purpose.
Begin with a brief that names the object, material, viewing angle, background and the few details that must be visible. For a product listing, request a front-facing ceramic storage jar on a light neutral surface, even illumination, a closed lid and clear space around the silhouette. If the scene must remain straightforward, say so explicitly rather than relying on the Utility name to encode all presentation choices. For a series of listing images, keep framing and background requirements consistent while changing the product description.
The V4.1 generation reference supports prompts up to 10,000 characters, preferred-colour and background-colour controls, a random seed and one to six outputs. A compatible saved style or optional reference images can guide appearance; the dedicated V4 Styles family is the separate line where a style is always mandatory. For optional references, use clear assets whose visual direction agrees. Exact colour reproduction from a reference is not guaranteed, so a brand-colour requirement still needs an explicit brief and a check of the output. For reference-style generation, use one to ten PNG, JPG or WebP images, no more than 64 MB in total and under 20 MB each. Each reference needs a shortest side of at least 256 pixels, a longest side of no more than 4,096 pixels and a resolution of no more than 16 megapixels. Use either these references or a compatible saved style, rather than both. For reference-style generation, flexible matching allows a looser interpretation, while precise matching follows the rendering, palette, composition and lighting more closely.
Recraft also documents image-to-image for the V4.1 line, combining an existing image with a prompt and strength from 0 to 1. A lower strength stays closer to the source and a higher value permits a larger change. This is useful when the starting composition or subject should inform a new version. It does not accept V4.1 custom style controls in the same transformation operation. Its producer image input limits are under 20 MB, up to 16 MP and sides between 256 and 4096 pixels.
Utility Pro shares the V4.1 restrictions on negative_prompt, curated style names, text_layout, artistic_level and no_text controls. Give a positive description of the intended scene and reserve precise lettering or layout work for an appropriate finishing step when needed. Review a product visual for the supplied material, shape and necessary details before treating it as a faithful listing asset. The useful result is a larger raster composition prepared for a clear product or mockup brief, while the exact product facts remain those supplied in the task.
POST /v1/images/generationstext, imageimage| Field | Type | Requirement | Values & limits | Default |
|---|---|---|---|---|
Fieldmodel | Typestring | RequirementRequired | Values & limits recraft/recraft-v4.1-utility-pro | Default— |
Fieldprompt | Typestring | RequirementRequired | Values & limits Minimum length: 1 | Default— |
Fieldaspect_ratio | Typestring | RequirementOptional | Values & limits 1:1, 4:3, 3:4, 16:9, 9:16, auto | Default— |
Fieldn | Typeinteger | RequirementOptional | Values & limits Minimum: 1 Maximum: 6 | Default— |
Fieldinput_references | Typearray | RequirementOptional | Values & limits Minimum items: 0 Maximum items: 1 | Default— |
Fieldprovider | Typeobject | RequirementOptional | Values & limits | Default— |
| Parameter | Contract |
|---|---|
Parametercontent_type | Contractapplication/json |
Parameterrequired | Contractmodel, prompt |
Parametermaterial_types | Contracttext, image |
Lifecycle: synchronous_result_then_owned_library
GET /v1/media/tasks/{task_id} · actual returned task_id or media library record
GET /v1/media/assets/{asset_id}/content
GET /v1/media/assets
GET /v1/media/assets/{asset_id}
The displayed rates estimate the cost before generation. The final charge is calculated from the cost recorded for the original generation. Measured output duration and forecast quantities are not the final billable quantity.
Tariff references do not add request options. Supported parameters are listed for the selected method.
Match each charge to the conditions shown. Use one rate for each set of alternative configurations.
| Configuration | Rate schedule | Forecast quantity | Billing unit | Charge |
|---|---|---|---|---|
| ConfigurationBase token rates | Rate scheduleBase rate | Forecast quantity— | Billing unit— | Charge Input · Input tokens · Estimate for comparison only — / 1K tokens Output · Output tokens · Estimate for comparison only — / 1K tokens Input · Cache read · Estimate for comparison only — / 1K tokens Input · Cache write · Estimate for comparison only — / 1K tokens Input · Cache write, 1 hour · Estimate for comparison only — / 1K tokens |
| Configurationoutput image | Rate schedule— | Forecast quantity— | Billing unitper output image | Charge Output · output image · Estimate for comparison only $0.42 per output image |
| ConfigurationEstimated generation cost | Rate schedule— | Forecast quantityone generation estimate | Billing unit— | Charge Output · Estimated generation cost · Estimate for comparison only $0.42 estimate before generation This estimate is not an additional charge or a fixed rate for the completed generation. |
Ailoot reserves an estimated amount before a request. After the result, it settles the final charge from measured usage. Streaming settlement uses the final usage record. How reservation and settlement work →
set -eu\n: "${AILOOT_API_KEY:?Set your Ailoot API key}"\nexport AILOOT_API_KEY\npython3 - <<'PY_REQUEST'\nimport json,os\nfrom pathlib import Path\np={'model': 'recraft/recraft-v4.1-utility-pro', 'prompt': 'a red panda astronaut floating in space, studio lighting'}\n\nPath("request.json").write_text(json.dumps(p,ensure_ascii=False))\nPY_REQUEST\ncurl --fail-with-body --silent --show-error https://api.ailoot.ai/v1/images/generations \\\n -H "Authorization: Bearer $AILOOT_API_KEY" -H 'Content-Type: application/json' \\\n --data-binary @request.json -D response-headers.txt -o result.json\npython3 - <<'PY_RESULT'\nimport base64, json, os, subprocess\nfrom pathlib import Path\nfrom urllib.parse import urlsplit, urljoin\n\ndef save_images(items):\n if not items: raise SystemExit("No completed images; retain the full response")\n for index, item in enumerate(items):\n encoded=item.get("b64_json")\n uri=item.get("url", "")\n if not encoded and uri.startswith("data:image/"):\n header, separator, encoded=uri.partition(",")\n if not separator or ";base64" not in header: raise SystemExit("Unsupported image data URI")\n if encoded:\n raw=base64.b64decode(encoded,validate=True)\n elif uri:\n uri=urljoin("https://api.ailoot.ai",uri)\n parsed=urlsplit(uri)\n if parsed.scheme!="https" or not parsed.netloc or parsed.username or parsed.password:\n raise SystemExit("Invalid returned image URL")\n owned=parsed.netloc=="api.ailoot.ai" and parsed.path.startswith("/v1/media/assets/") and parsed.path.endswith("/content")\n args=["curl","--fail-with-body","--silent","--show-error",uri]\n if owned: args += ["-H","Authorization: Bearer "+os.environ["AILOOT_API_KEY"]]\n temporary=Path(f"image-{index}.bin")\n subprocess.run(args+["-o",str(temporary)],check=True)\n raw=temporary.read_bytes()\n temporary.unlink()\n else: raise SystemExit("Image has neither bytes nor URL")\n if not raw: raise SystemExit("Empty image result")\n ext="png" if raw.startswith(b"\\x89PNG") else "jpg" if raw.startswith(b"\\xff\\xd8") else "webp" if raw[:4]==b"RIFF" and raw[8:12]==b"WEBP" else "svg" if raw.lstrip().startswith((b"<svg",b"<?xml")) else "bin"\n Path(f"image-{index}.{ext}").write_bytes(raw)\n print("Every returned image saved; complete response metadata retained")\nsave_images(json.loads(Path("result.json").read_text())["data"])\nPY_RESULT\nDownload each returned image or save its Base64 contents
GET /v1/media/tasks/{task_id}GET /v1/media/assets/{asset_id}/contentGET /v1/media/assetsGET /v1/media/assets/{asset_id}set -eu\n: "${AILOOT_API_KEY:?Set your Ailoot API key}"\ncurl --fail-with-body --silent --show-error https://api.ailoot.ai/v1/media/assets \\\n -H "Authorization: Bearer $AILOOT_API_KEY" -o owned-assets.json\n# Preserve every returned asset and follow its exact signed content URL. Do not construct a signed token.\nSave every completed image; retrieve each returned URL or decode its Base64 contents.
Retain the complete response and headers, every actual output, original returned identifiers and all usage fields. Recover the original operation without submitting creation again.
Keep the returned X-Client-Request-ID for reconciliation. Read only actual returned task_id/asset_id values or the owned media library; never build a task URL from the operation ID and never resubmit creation.
| Field | Type |
|---|---|
Fieldcreated | Type |
Fielddata[].url | Type |
Fielddata[].b64_json | Type |
Fieldusage | Type |
Ailoot Ultra recraft/recraft-v4.1-utility-pro
/v1/images