Technical Specifications of mj-fast-reroll
| Specification | Details |
|---|---|
| Model ID | mj-fast-reroll |
| Provider family | Midjourney-style image generation / reroll operation (cometapi.com) |
| Primary function | Re-run or reroll an existing Midjourney task to generate a fresh result set based on the same prompt lineage |
| API type | Task-based API that simulates Midjourney Discord-style button interactions rather than a simple one-shot REST image endpoint (apidoc.cometapi.com) |
| Mode | Fast mode variant of the reroll workflow |
| Pricing on CometAPI | $0.056 per request (cometapi.com) |
| Commercial use | Supported on the CometAPI model page (cometapi.com) |
| Input pattern | Typically requires a previously created Midjourney task context, since reroll is a follow-up operation in the task state machine (apidoc.cometapi.com) |
| Output | A new image-generation task result corresponding to the rerolled request (apidoc.cometapi.com) |
What is mj-fast-reroll?
mj-fast-reroll is a Midjourney-oriented API operation exposed through CometAPI for rerolling an existing generation in fast mode. In practice, “reroll” means requesting a fresh generation pass from the same prompt and interaction branch, similar to pressing a reroll button in the Midjourney workflow.
Unlike a plain text-to-image endpoint that starts from scratch each time, this model fits into a stateful Midjourney task flow. CometAPI’s Midjourney quick-start documentation explains that these APIs simulate Discord button interactions, where each step returns the next valid actions. That makes mj-fast-reroll especially useful when your application needs to continue from an already generated job and quickly obtain alternative results without rebuilding the whole interaction manually. (apidoc.cometapi.com)
On CometAPI, the model is listed under the Midjourney family with per-request billing and commercial-use support. (cometapi.com)
Main features of mj-fast-reroll
- Fast reroll workflow: Designed for fast-mode Midjourney reruns, helping developers regenerate variations more quickly than relax-mode equivalents.
- Midjourney button/state compatibility: Works within a state-machine interaction model that mirrors Midjourney button actions, which is important for apps that automate follow-up generation steps. (apidoc.cometapi.com)
- Prompt lineage reuse: Lets you reuse the context of an existing generation branch instead of reconstructing the workflow from the beginning. This is an inference based on how reroll operations are categorized in Midjourney API docs.
- Production-friendly billing: CometAPI lists the model at a fixed per-request price of $0.056, which makes cost estimation straightforward for batch or user-triggered image retries. (cometapi.com)
- Commercial-use availability: The CometAPI listing marks the model as available for commercial use, which is relevant for SaaS products, creative tools, and internal automation pipelines. (cometapi.com)
- Unified access via CometAPI: As part of CometAPI’s aggregated model catalog, it can be integrated through the platform’s unified API approach rather than requiring a separate provider-specific setup. (cometapi.com)
How to access and integrate mj-fast-reroll
Step 1: Sign Up for API Key
Sign up on CometAPI and create your API key in the dashboard. Once generated, store it securely and use it as your Bearer token for all requests to the mj-fast-reroll API.
Step 2: Send Requests to mj-fast-reroll API
Send requests through CometAPI using the model ID mj-fast-reroll. Because this is a Midjourney-style task workflow, you will typically call it as a follow-up action tied to an existing task or button state, rather than as a completely standalone generation. CometAPI’s Midjourney documentation notes that these APIs behave like a state machine, so your request flow should preserve the task context returned by earlier steps. (apidoc.cometapi.com)
curl https://api.cometapi.com/v1/responses \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $COMETAPI_API_KEY" \
-d '{
"model": "mj-fast-reroll",
"input": {
"task_id": "your_previous_midjourney_task_id"
}
}'
Step 3: Retrieve and Verify Results
After submission, retrieve the generated result using the task or response ID returned by CometAPI. Verify that the rerolled output matches the expected Midjourney branch and status before displaying it to end users or sending it into downstream editing workflows. Since Midjourney-style APIs are asynchronous and state-driven, result polling or callback-based verification is typically part of a reliable integration. (apidoc.cometapi.com)