mj_turbo_variation

Technical Specifications of mj-turbo-variation

What is mj-turbo-variation?

mj-turbo-variation is a specialized image-generation endpoint for producing fast variations of an existing Midjourney-style image. Rather than generating from scratch, it is intended for iterative workflows where you already have a base image and want closely related alternatives with new details, composition adjustments, or stylistic shifts.

Online documentation around Midjourney-compatible APIs consistently describes “variation” as a post-generation action that creates alternate versions from a prior result, while “turbo” refers to the highest-speed processing mode for supported jobs. Midjourney’s own documentation describes Turbo Mode as a faster GPU speed option, and third-party Midjourney API providers commonly expose variation as a distinct operation or endpoint.

In practice, that means mj-turbo-variation is best understood as a rapid-iteration model identifier on CometAPI: you submit a variation request tied to an existing image or job, and the service returns new candidate images that stay near the original visual idea while exploring alternative outputs. This interpretation is an inference based on the naming convention and the behavior described across Midjourney and Midjourney-compatible API documentation.

Main features of mj-turbo-variation

• Fast variation generation: Designed for speed-first image iteration, making it useful when you need alternate outputs quickly without rerunning a slower full generation workflow.
• Built for iterative creativity: Best suited to refining an existing image concept rather than producing a brand-new composition from only a text prompt. Variation workflows are typically used after an initial render.
• Preserves core visual intent: Variation operations generally keep the source image’s overall direction while changing details, layout emphasis, styling, or composition.
• Useful for design exploration: Ideal for concept art, marketing visuals, thumbnails, moodboards, and any workflow where multiple close alternatives help with selection. This is a practical inference from how variation endpoints are described and used in Midjourney-style pipelines.
• Fits asynchronous API pipelines: Midjourney-compatible services commonly handle these jobs as submitted tasks that are later queried for completion and results, which makes the model suitable for backend automation.
• Turbo-mode workflow alignment: Midjourney documentation indicates turbo support for vary/remix-style jobs, which matches the expected purpose of a turbo variation model identifier.

How to access and integrate mj-turbo-variation

Step 1: Sign Up for API Key

To get started, create an account on CometAPI and generate your API key from the dashboard. You’ll use this key to authenticate all requests to the mj-turbo-variation API. Store it securely in an environment variable such as COMETAPI_API_KEY.

Step 2: Send Requests to mj-turbo-variation API

Use CometAPI's Midjourney-compatible endpoint at POST /mj/submit/action.

curl https://api.cometapi.com/mj/submit/action \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $COMETAPI_API_KEY" \
  -d '{
    "prompt": "a futuristic cityscape at sunset --v 6.1",
    "botType": "MID_JOURNEY",
    "accountFilter": {
      "modes": ["TURBO"]
    }
  }'

Step 3: Retrieve and Verify Results

The API returns a task object with a task ID. Poll GET /mj/task/{task_id}/fetch to check generation status and retrieve the output image URL when the task reaches a terminal state.