bria/image-edit-increase-resolution with the Comfy Router API. Bria provides the model; Router gives it the shared authentication and request route below.
Quick start
Create a key at platform.comfy.org/profile/api-keys and export it asCOMFY_API_KEY. The Python and TypeScript snippets use the Comfy SDKs (pip install comfy-sdk, npm install @comfyorg/sdk); the cURL snippet is the same call over raw HTTP.
Model ID: bria/image-edit-increase-resolution
Endpoint: POST https://api.comfy.org/v2/models/bria/image-edit-increase-resolution
Schema
Input
integer
Resolution multiplier to apply. Supported values are 2 and 4. Maximum output resolution is 8192x8192.
string
required
The image to upscale. Supported input types are Base64-encoded string or URL pointing to a publicly accessible image file. Accepted formats JPEG, JPG, PNG, WEBP.
boolean
Controls whether partially transparent areas from the input image are retained in the output.
boolean
When false (default), the request is processed asynchronously. When true, the API holds the connection open until complete.
boolean
When enabled, applies content moderation to input visual. Returns 422 if the image fails moderation.
boolean
When enabled, applies content moderation to result visual. Returns 422 if the output fails moderation.
GET /v2/models/bria/image-edit-increase-resolution/openapi.json, the same document it validates a call against before the request reaches the provider.
Output
Router does not publish an output schema for this model.Examples
Input
Before you ship
Save oneIdempotency-Key for each call and reuse it for retries. Router can hold the connection for up to 10 minutes. The SDKs handle authentication; raw HTTP clients send the headers themselves.
When a request fails, Router sends an X-Comfy-Error-Type response header explaining why. A 422 means Router rejected the input before calling the provider. Download generated assets promptly because result URLs can expire.
Headers
Authentication, idempotency, request IDs, error buckets, retry pacing, spend limits.
Using the Router API
Model discovery, validation errors, retries, and billing.
Limitations
What Router does not do today, and what to use instead.