Firefly Upscale API vs Sume's image_upscale_create tool
Firefly's Upscale API enhances resolution at 2x, 4x or 6x. Sume exposes upscaling as the image_upscale_create MCP tool: a paid job you poll.

Firefly's Upscale API enhances image resolution and quality, with 2x, 4x or 6x scale factors in its user-assets use case. On Sume, image upscaling is the image_upscale_create tool in the hosted MCP server: a paid write tool that needs an idempotency_key and returns a job you read with the standard status and result calls.
Adobe facts are from its API overview; Sume facts from MCP tools and gates and Jobs and results, read 2026-10-01.
What does the Firefly Upscale API cover?
Adobe lists two use cases. User Assets Upsampler increases the resolution of your own photos and artwork while following the source closely, at 2x, 4x or 6x. Generated Image Upsampler keeps crispness and coherent fine detail, such as fabric or grass textures, in AI-generated images.
How does upscaling work on Sume?
The MCP tools page lists image_upscale_create among the paid tools that take an idempotency_key. Like other Sume jobs, you then poll status and fetch the result. The Image API docs name the same pattern: poll GET /v1/jobs/{id}/status and fetch GET /v1/jobs/{id}/result.
| Topic | Firefly Upscale API | Sume |
|---|---|---|
| Entry point | Upscale API in Firefly Services | image_upscale_create MCP tool |
| Scale factors on the page | 2x, 4x, 6x | Not listed in the sources used here |
| Reading output | Not covered on the overview | Job status, then job result |
Should I wait inside one call?
No. The jobs docs say "30 seconds is a wait budget, not a job duration". If a call returns before the job is terminal, keep the job id and read it again rather than resubmitting a paid request. See AI image upscale API for the broader picture.
Which one fits my workflow?
If you already run inside Adobe's service and need a specific scale factor, the Firefly page is the reference. If your pipeline already talks to Sume through MCP or REST jobs, the upscale tool keeps the same job model as generation. Check the tool's input schema in your MCP client for the parameters it accepts.
Sources
Related posts
More in Developers
- drama-3-preview model id vs Sume TTS Router model ids
Fish selects drama-3-preview with a model header. Sume TTS Router takes a required model id from its catalog, and unknown ids fail with 400 model_not_found.
- Fix lens distortion in video by API with lenscorrection
Sume's video filter allowlists ffmpeg's lenscorrection, so barrel distortion from a wide action-cam clip can be corrected by coefficients you choose and test.
- FLUX.2 JSON prompt: on Sume it is text in the prompt field
BFL says FLUX.2 accepts JSON-structured prompts. On Sume, prompt is a plain string, so JSON goes in as text; other fields are typed.
- FLUX.2 LoRA API: finetune_id on BFL, not on Sume
BFL serves klein LoRAs through -finetuned endpoints with finetune_id. Sume rejects provider-specific parameters, so use reference images instead.
Written by Sume