Ideogram Topaz Bloom 2 creative upscale prompt vs Sume upscale

Ideogram's Topaz Bloom 2 endpoint creatively upscales an image 2x, 4x, or 8x and accepts an optional prompt that guides the detail it regenerates. Sume's image upscale takes a public image_url and an upscale_factor and has no prompt field, so a prompt-guided creative upscale is not something to send there.

Ideogram facts are from its Topaz Bloom 2 page, read 2026-10-01. Sume facts are from the OpenAPI document and the docs.

What does the Topaz Bloom 2 request look like?

It is POST /v2/image/upscale/topaz-bloom-2 with multipart/form-data. The image file is required and can be up to 50MB. prompt is optional; leave it empty to enhance the source as-is. creativity runs from 1 (most faithful) to 9 (most creative), and color_preservation defaults to true. Results return directly by default, or set async or webhook_url to poll a generation_id.

What does Sume's upscale request accept?

The route is POST /v1/image-upscale-1.0/upscale, and the MCP tool name is image_upscale_create (listed as a paid tool that takes an idempotency_key; see MCP tools and gates). The OpenAPI schema sets additionalProperties to false and lists image_url, upscale_factor (1 to 4, default 2), output_format (png, jpg, webp), metadata, mode, and webhook_url. A prompt is not in that list.

Where can I still use a prompt?

If you want text direction on the result, send the image as a reference to an image edit with a prompt instead; that is a regeneration, not an upscale. See the Sume image upscale API for the plain route.

What must the input URL satisfy?

Input image URLs must be fetchable public HTTPS URLs. Localhost, private-network, non-HTTPS, and signed or private URLs are rejected before submission (asset library docs). Host the file first, then pass the URL.