image-router

Route image generation requests by detecting the image category—such as product, face, full-body, vehicle, interior, or UGC—and matching it to an optimal provider and workflow template, while deriving compatible generation parameters like size, steps, and batch size.

Yes, you can specify a quality tier to automatically derive deterministic generation parameters, including CFG, sampler, negative prompts, steps, and batch size, tailored to the detected image category and the requested quality level.

LoRA registry matching checks for approved, category and brand-matching LoRAs during image routing and recommends their usage to enhance generation, but it does not block the image generation request if no matching LoRA is found.

For brand-specific product packshots, submit the image request with the brand name and quality tier, allowing the router to detect the product category, apply optional LoRA registry matching, and output a structured JSON routing decision.

Yes, provider routing supports requested provider overrides, allowing you to bypass the default routing logic and direct the image generation request to a specific provider while still computing the necessary workflow template and generation parameters.

Automated workflow template routing supports product, face, full-body, vehicle, interior, and UGC-style image requests, categorizing each request to select the appropriate provider, workflow, and generation parameters.