mj_turbo_shorten

Technical Specifications of mj-turbo-shorten

What is mj-turbo-shorten?

mj-turbo-shorten is CometAPI’s platform identifier for a Midjourney-compatible prompt-shortening capability that combines Midjourney’s /shorten behavior with Turbo mode routing. Midjourney’s official command list describes /shorten as a way to submit a long prompt and receive suggestions to make it more concise, and it separately lists /turbo as the mode switch for Turbo operation. Third-party Midjourney proxy implementations commonly expose this through a dedicated shorten endpoint under the Turbo path, typically /mj-turbo/mj/submit/shorten.

In practice, this model ID is best understood not as a general-purpose text LLM, but as a task-oriented Midjourney helper endpoint for prompt optimization. It is designed for developers or creators who already have a detailed image prompt and want the system to analyze that prompt, identify compressible wording, and return a more concise formulation suitable for continued Midjourney workflows.

Because Midjourney-style proxy APIs are usually asynchronous, a shorten request is generally submitted first and then checked later using a task fetch endpoint. Documentation from Midjourney proxy-compatible providers shows this pattern clearly: submit the shorten task, receive a task ID, then poll /mj/task/{id}/fetch to retrieve status and results.

Main features of mj-turbo-shorten

• Prompt condensation: Helps reduce long Midjourney prompts into more concise versions, aligned with Midjourney’s /shorten function.
• Turbo-mode routing: Uses the Turbo path convention used by Midjourney proxy implementations, typically under /mj-turbo/mj, for users who want the shorten workflow associated with Turbo mode.
• Midjourney-compatible API pattern: Fits the broader Midjourney proxy ecosystem, where endpoints are organized by actions such as imagine, describe, shorten, action, modal, and fetch.
• Asynchronous task workflow: Requests are usually submitted as jobs rather than returning the final result immediately, which makes it suitable for queue-based image workflow systems.
• Simple text input: The shorten operation mainly requires a text prompt, with implementations commonly also accepting botType such as MID_JOURNEY.
• Workflow support for prompt refinement: Useful before image generation when you want to simplify wording, remove redundancy, or prepare a cleaner prompt for later Midjourney calls. This is an inference from the documented /shorten behavior and proxy endpoint design.

How to access and integrate mj-turbo-shorten

Step 1: Sign Up for API Key

Sign up on CometAPI and generate your API key from the dashboard. After that, store it securely and use it in the Authorization: Bearer YOUR_API_KEY header for all requests to the mj-turbo-shorten API.

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

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

curl https://api.cometapi.com/mj/submit/shorten \
  -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.