bria/fibo 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/fibo
Endpoint: POST https://api.comfy.org/v2/models/bria/fibo
Schema
Input
Router has not published an authored input schema for this model yet:
GET /v2/models/bria/fibo/openapi.json returns an open object with x-comfy-input-schema-authored: false. Router forwards the body to Bria unchanged, so Bria’s own API reference is authoritative for the request fields, and nothing is validated server side.Output
object
Error object (only present when status is ERROR)
integer
Error code.
string
Additional error details.
string
Error message.
string
Unique identifier for the request.
object
Result object (only present when status is COMPLETED)
string
URL of the generated/edited image.
string
Original prompt.
string
Refined version of the prompt.
integer
Seed used for generation.
string
The detailed JSON structured prompt.
string
URL of the generated video.
string
Current status of the request.Possible values:
IN_PROGRESS, COMPLETED, ERROR, UNKNOWNExamples
Output
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.
Use X-Comfy-Error-Type to classify a failure. 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
Find models, inspect schemas, and retry safely.
Limitations
What Router does not do today, and what to use instead.