Technical Specifications of mj-fast-upload
| Specification | Details |
|---|---|
| Model ID | mj-fast-upload |
| Provider family | Midjourney-compatible image generation workflow (cometapi.com) |
| Primary modality | Text-to-image, with Midjourney workflow support exposed through API-based task submission and result retrieval (apidoc.cometapi.com) |
| Access type | API model available through CometAPI’s unified model catalog (cometapi.com) |
| Pricing on CometAPI | $0.008 per request, with commercial use indicated on the model page (cometapi.com) |
| Integration pattern | Submit a generation task, then poll or retrieve task results and action buttons based on the API response flow described in the Midjourney quick-start docs (apidoc.cometapi.com) |
| Typical output | Generated image tasks and follow-up actions such as downstream Midjourney button operations, depending on version and returned response data (apidoc.cometapi.com) |
What is mj-fast-upload?
mj-fast-upload is a CometAPI-exposed Midjourney model endpoint intended for fast image-generation task submission in a Midjourney-style workflow. Based on CometAPI’s model listing and Midjourney quick-start documentation, it is designed for developers who want to trigger image generation through a unified API rather than interacting with Midjourney manually.
While CometAPI’s public model page gives only a brief description, the surrounding documentation shows that Midjourney integrations on the platform use an asynchronous task pattern: you send a request, receive task metadata, and then retrieve output details and any available follow-up actions from the API response. That makes mj-fast-upload suitable for apps that need automated image generation pipelines, creative tooling, internal dashboards, or production workflows that depend on programmatic image creation.
Main features of mj-fast-upload
- Fast task submission: The model is positioned as a fast-upload Midjourney endpoint, indicating an optimized path for sending generation jobs into a Midjourney-compatible API workflow.
- Midjourney-style image generation: It is part of CometAPI’s Midjourney model lineup and is intended for prompt-based image creation through API calls rather than a manual UI flow.
- Asynchronous workflow support: CometAPI’s Midjourney quick-start shows a submit-then-retrieve pattern, which is important for apps that need queue handling, background jobs, or task-state tracking.
- Follow-up action compatibility: The documentation notes that button labels and custom IDs can vary by Midjourney version, implying support for downstream actions such as post-generation operations driven by API response metadata.
- Commercial usage availability: The CometAPI listing explicitly marks the model as available for commercial use.
- Low per-request pricing: CometAPI lists
mj-fast-uploadat $0.008 per request, which makes it straightforward to estimate costs for batch or production usage. - Unified platform integration: Because it is listed in CometAPI’s catalog, developers can access it through the platform’s standardized authentication and API workflow instead of building a separate provider-specific integration.
How to access and integrate mj-fast-upload
Step 1: Sign Up for API Key
Sign up on CometAPI and create an API key from your dashboard. Once your account is ready, you can use the same credential structure used across CometAPI’s unified API platform to authenticate requests for mj-fast-upload. CometAPI exposes this model in its model catalog, and the Midjourney quick-start documentation provides the API workflow reference you can use during implementation.
Step 2: Send Requests to mj-fast-upload API
Use CometAPI's Midjourney-compatible endpoint at POST /mj/submit/upload-discord-images.
curl https://api.cometapi.com/mj/submit/upload-discord-images \
-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": ["FAST"]
}
}'
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.