Technical Specifications of mj-turbo-imagine
| Specification | Details |
|---|---|
| Model ID | mj-turbo-imagine |
| Provider on CometAPI | Midjourney |
| Model type | Text-to-image generation |
| Access pattern | Asynchronous task-based API |
| Speed tier | Turbo |
| Primary use | Rapid image generation from natural-language prompts |
| Request flow | Submit an imagine task, receive a task ID, then query task status and results |
| Endpoint pattern | Turbo requests use the /mj-turbo path prefix, for example /mj-turbo/mj/submit/imagine |
| Output | Generated image results, typically returned through task query responses with image links and actionable metadata |
| Related operations | Task query, action/button-style follow-up operations, and modal handling when required |
What is mj-turbo-imagine?
mj-turbo-imagine is CometAPI’s platform identifier for the Midjourney Turbo imagine workflow, used to submit high-speed image generation requests through CometAPI’s unofficial Midjourney-compatible API layer. CometAPI describes Midjourney access as an unofficial integration that lets developers send prompts and retrieve generated images through a REST-style interface rather than interacting directly with Midjourney’s native product surfaces. cometapi.com
In practice, this model is designed for developers and businesses that want fast text-to-image generation in automated workflows. The “imagine” operation is the entry point for creating new images from prompts, while the Turbo speed tier prioritizes faster turnaround than lower-speed modes. CometAPI’s documentation explains that the Midjourney flow begins by generating an image task, then polling for results, and optionally triggering follow-up actions on the returned image grid. apidoc.cometapi.com
Because this model is exposed through CometAPI, mj-turbo-imagine fits well into programmatic use cases such as creative tooling, design prototyping, marketing asset generation, and prompt-driven image pipelines where quick response time matters. The model page and API tutorial indicate that CometAPI wraps Midjourney generation into a unified API experience alongside other AI models. cometapi.com
Main features of mj-turbo-imagine
- Turbo-speed image generation: This model is mapped to the Turbo path and is intended for faster image creation than standard or lower-speed Midjourney modes, making it suitable for time-sensitive generation workflows. apidoc.cometapi.com
- Prompt-based image creation: The imagine workflow generates images from natural-language prompts, serving as the core text-to-image entry point in the Midjourney process. cometapi.com)
- Asynchronous task workflow: Requests return a task ID first, after which you query the task to retrieve status, image links, and any follow-up controls. This is useful for queue-based or backend processing systems. apidoc.cometapi.com
- Actionable result handling: After generation, returned results can include buttons or custom action identifiers for downstream operations such as additional image actions, enabling multi-step creative workflows. apidoc.cometapi.com
- REST-style integration through CometAPI: CometAPI abstracts the underlying Midjourney interaction into a more standard API pattern, which simplifies integration into apps, services, and automation platforms. cometapi.com
- Unified platform access: The model is part of CometAPI’s broader multi-model catalog, which can be useful for teams that want to manage image and other AI capabilities through one provider account and API surface. cometapi.com
How to access and integrate mj-turbo-imagine
Step 1: Sign Up for API Key
To begin, visit the CometAPI website and create an account. After registration, you’ll receive an API key, which is essential for authenticating your requests. cometapi.com
Step 2: Send Requests to mj-turbo-imagine API
Use CometAPI’s Midjourney submission flow to send an imagine request for mj-turbo-imagine. Turbo requests use the /mj-turbo path prefix, for example /mj-turbo/mj/submit/imagine. The API workflow starts by submitting the generation request, which responds with a task ID. You should authenticate with your bearer token and send a JSON payload containing your prompt and required parameters. apidoc.cometapi.com
Step 3: Retrieve and Verify Results
After submitting the request, use the task query interface to check the task ID and retrieve the generated result. CometAPI’s Midjourney tutorial explains that the query response can contain image links and buttons or custom IDs for additional operations. If you want to continue with actions such as follow-up image operations, use the returned identifiers to submit the next request and keep polling until the workflow is complete. apidoc.cometapi.com
.png)