FLUX 1.1 Pro Ultra MCP guide for polished images
Evaluate the catalog-listed FLUX 1.1 Pro Ultra entry and verify its live Studio model ID before any generation call.
This is a blocked procedure, not a copy-ready generation recipe. Connect the recommended remote OAuth MCP and complete browser sign-in, then call `list_models`. If the response does not establish the exact FLUX 1.1 Pro Ultra entry and its ID, stop and return to the parent model directory. Do not infer an ID from the display name, page slug, fal endpoint, or an old example.
If a later first-party Studio response verifies the ID, call `get_credits` to return the current balance and present the sourced ID, displayed cost, prompt, and any model-specific ratio evidence for approval. Do not treat the shared request enum as proof that this entry accepts a particular ratio. In the published package, `generate` with `wait: true` polls for completion or failure for up to 120 seconds; the separate `wait_generation` tool accepts a timeout from 5 to 300 seconds. Waiting changes polling behavior, not creative approval.
Evaluate FLUX 1.1 Pro Ultra against a named still-image brief
The current OfflineCreator catalog lists FLUX 1.1 Pro Ultra as a text-to-image entry, labels its fit “photoreal detail,” and charges 8 Studio credits per generation. Treat that fit label as Studio positioning, not comparative evidence. It does not establish that this entry produces more detail, stronger campaign work, or better results than another model on a particular prompt.
Use a written acceptance rubric if the entry is eventually verified in the live catalog: define the subject, composition, lighting, material behavior, edge clearance, and text policy before spending credits. No matched output test was performed for this guide, so it makes no claim about typography, identity consistency, runtime, reliability, or approval rates.
- Studio model
- FLUX 1.1 Pro UltraCurrent catalog workflow: text-to-image; current catalog fit: photoreal detail.
- Studio cost
- 8 credits per generationRecheck the live catalog before submitting because this page has a monthly freshness cadence.
Resolve the Studio ID live and keep upstream identifiers separate
The fetched public Studio pages name FLUX 1.1 Pro Ultra, its 8-credit cost, and its “photoreal detail” fit, but they do not display a current internal model ID. The published MCP package says `list_models` returns the launch catalog and that `generate` expects an ID from that response. Because this required evidence is missing, this page cannot supply an executable `modelId`, cannot become review-ready, and must remain an honest researched draft.
Consolidate this unresolved model-specific topic into the parent MCP model directory until a current Studio first-party source establishes the exact ID. fal documents `fal-ai/flux-pro/v1.1-ultra` as an upstream endpoint, but the reviewed evidence does not prove a Studio mapping. Never substitute that provider endpoint for the missing Studio ID.
- OfflineCreator model ID
- Missing required evidenceExecution and review-ready status are blocked until a current first-party Studio response establishes the exact ID.
- fal upstream endpoint
- `fal-ai/flux-pro/v1.1-ultra`An upstream fal identifier only; no current Studio-to-fal mapping is claimed.
Budget the polish pass before generating
At the current catalog rate, one FLUX 1.1 Pro Ultra call costs 8 Studio credits. Two approved variations cost 16 credits and four cost 32 credits. Those totals are simple catalog arithmetic, not an estimate of how many images a brief will need. Separate exploration from polish so the operator can stop after an acceptable frame rather than consuming a predeclared batch automatically.
Write the stop condition before the first paid call: for example, approve one square product master only if the silhouette is intact, reflections look physically plausible, the focal object has enough negative space for live copy, and no generated lettering appears in the product area. Rejecting an image against named criteria is more auditable than adding vague prompt adjectives and repeatedly spending credits.
- One generation
- 8 creditsCurrent Studio catalog rate, subject to monthly re-verification.
- Two shortlisted variations
- 16 creditsPlanning arithmetic only; this is not a recommended minimum.
- Four variations
- 32 creditsRequire an explicit reason before widening the shortlist.
Treat the ratio enum as syntax, not model support
The published OfflineCreator MCP 0.1.1 `generate` schema validates `16:9`, `9:16`, or `1:1` and describes `16:9` as the request default. That shared enum does not establish which ratio FLUX 1.1 Pro Ultra accepts, what dimensions Studio returns, or whether the request reaches the provider unchanged. This draft therefore supplies no executable ratio recommendation for the named entry.
The upstream fal endpoint documents a broader set: `21:9`, `16:9`, `4:3`, `3:2`, `1:1`, `2:3`, `3:4`, `9:16`, and `9:21`. Those are direct-provider options, not Studio evidence. Do not pass any ratio for this named Studio entry until a current first-party Studio record binds its exact returned model ID to that ratio. A placement requirement such as `4:5` remains a delivery requirement, not proof of a native Studio path.
- Shared MCP request enum
- `16:9`The schema default; not verified as FLUX 1.1 Pro Ultra compatibility.
- Shared MCP request enum
- `9:16`A syntactically accepted value; not verified for this named entry.
- Shared MCP request enum
- `1:1`A syntactically accepted value; not a model-specific capability claim.
Consolidate into the parent hub until the ID is sourced
The page's overlap guard requires consolidation when model ID, cost, fit, and ratios cannot all be evidenced. Cost, fit, and the generic MCP ratio schema are documented, but the model-specific Studio ID is not. Treat the parent MCP model directory as the maintained next action rather than promoting or executing this leaf guide. Use the evaluation guide only after a live catalog response closes the ID gap.
Keep this researched draft blocked and consolidated
The verified page-specific facts are narrow: Studio publishes an 8-credit text-to-image entry with the fit label “photoreal detail,” while the MCP package defines a shared ratio enum and requires a `modelId` from `list_models`. The reviewed current Studio sources establish neither the ID nor model-specific ratio compatibility for this named entry. Those missing required fields block execution and review-ready status. Keep the leaf as a researched, unreviewed draft and consolidate its actionable guidance into `/models/mcp-model-guides` until first-party evidence closes both gaps.
A fresh last30days pass collected recent FLUX 3, Flux.2, and unrelated MCP chatter, but no OfflineCreator Ultra practitioner thread that closes the ID or ratio gaps. Do not describe FLUX 1.1 Pro Ultra as Black Forest Labs' latest family. In July 2026, Black Forest Labs announced FLUX 3 as a new multimodal foundation model in Early Access and said FLUX 3 Image early access would follow. That announcement does not prove a Studio catalog change or a quality comparison; it is included only as a model-freshness boundary.