Technical Specifications of mj-turbo-upscale
| Specification | Details |
|---|---|
| Model ID | mj-turbo-upscale |
| Provider category | Midjourney image upscaling model on CometAPI. |
| Primary function | Upscales previously generated Midjourney images into higher-resolution outputs for download, sharing, or production workflows. |
| Input requirement | Typically requires a previously generated image task reference plus the selected image index from the original 4-image grid. |
| Output type | Higher-resolution image result derived from an existing Midjourney generation. |
| Workflow type | Post-processing / image enhancement rather than first-pass image generation. |
| Typical resolution behavior | Midjourney’s current upscale flow commonly doubles image dimensions; for example, a 1:1 image can go from 1024×1024 to 2048×2048. |
| API style | Request-based API access through CometAPI, with model availability listed under its Midjourney catalog. |
| Commercial use | Listed as supporting commercial use on CometAPI. |
| Pricing on CometAPI | CometAPI lists mj-turbo-upscale at $0.016 per request on the referenced model page. |
What is mj-turbo-upscale?
mj-turbo-upscale is CometAPI’s platform identifier for a Midjourney upscaling model endpoint. Its role is not to create a brand-new image from scratch, but to take an image that has already been generated in a Midjourney workflow and produce a larger, higher-quality version suitable for delivery, presentation, or downstream creative use.
Based on publicly available Midjourney upscaling documentation, this kind of model is used after a generation step, when you have selected one image from a generated set and want a cleaner, larger final output. Midjourney describes upscaling as the step that makes an image “bigger and better,” and current versions commonly double the resolution of the original image.
In practical API terms, upscaling endpoints usually depend on the original generation task ID and a chosen image index, which makes mj-turbo-upscale best understood as a fast enhancement endpoint for existing Midjourney outputs rather than a standalone text-to-image model.
Main features of mj-turbo-upscale
- Higher-resolution output: Designed to transform an already generated Midjourney image into a larger, more usable final asset.
- Built for post-generation workflows: Works after the initial image creation step, making it useful in approval pipelines where users first generate options and then upscale the selected result.
- Selection-based processing: Common Midjourney upscale APIs operate on a chosen image index from the original 4-image set, which fits standard Midjourney selection flows.
- Useful for delivery and print-oriented use cases: Public Midjourney API documentation explicitly notes that upscaled results are better suited to high-resolution use, including printing scenarios.
- Supports asynchronous integration patterns: Midjourney upscale APIs commonly support callback URLs so applications can receive completion notifications without blocking.
- Commercially usable through CometAPI: CometAPI lists the model as available for commercial use, which is important for production integrations.
- Low per-request cost: CometAPI’s model page lists a per-request price, making usage predictable for teams building image-processing pipelines.
How to access and integrate mj-turbo-upscale
Step 1: Sign Up for API Key
To access the mj-turbo-upscale API, first register for a CometAPI account and generate your API key from the dashboard. You will use this key to authenticate every request to the mj-turbo-upscale endpoint. Keep the key secure and load it from an environment variable or secret manager in production systems. CometAPI lists API resources and sample code for this model on its model page.
Step 2: Send Requests to mj-turbo-upscale API
Send a request to the mj-turbo-upscale API using your standard CometAPI-compatible client or HTTP stack, specifying mj-turbo-upscale as the model ID. Because this is an upscale workflow, your request should be tied to a previously generated Midjourney task and the image selection you want to upscale. Public Midjourney upscale API patterns commonly require a task ID and an image index, and may also support optional watermark or callback parameters.
curl --request POST \
--url https://api.cometapi.com/v1/images \
--header "Authorization: Bearer $COMETAPI_API_KEY" \
--header "Content-Type: application/json" \
--data '{
"model": "mj-turbo-upscale",
"input": {
"task_id": "YOUR_PREVIOUS_TASK_ID",
"image_index": 0
}
}'
Step 3: Retrieve and Verify Results
After submitting the request, retrieve the result either by polling the task status or by receiving it through your configured callback workflow, depending on your integration design. Verify that the returned asset is the correct upscaled variant, confirm resolution and visual fidelity, and then store or deliver the final image to your application, CMS, or customer-facing workflow. Midjourney’s official documentation indicates that upscale operations are intended to produce the larger final downloadable version of an image.