# Bria | Virtual Try-On BRIA Virtual Try-On turns person and garment photos into a try-on image that preserves pose, background, and garment details for fashion previews. ## API Information - **Model Slug:** bria-virtual-try-on - **Branded URL:** https://www.eachlabs.ai/bria/bria/bria-virtual-try-on - **Provider:** Bria - **Category:** Image to Image - **Output Type:** image - **Status:** active - **Base Cost:** $0.04 per execution - **Interactive Demo:** https://www.eachlabs.ai/ai-models/bria-virtual-try-on ## Pricing - **Charge Type:** dynamic - **Estimate:** $0.04 per execution - **Pricing Details:** default: $0.04 ## Input Schema | Parameter | Type | Required | Default | Constraints | Description | |-----------|------|----------|---------|-------------|-------------| | person_image | string | Yes | - | - | Photo of the person to edit. Supported provider formats: JPEG, JPG, PNG, and WEBP. | | garment_images | array | Yes | - | - | One to three garment or accessory image URLs to put on the person. Send a full outfit together to change several items in one call. | | instruction | string | No | - | - | Optional styling direction. Use only the detail you want to steer rather than a full prompt. | | aspect_ratio | string | No | - | 1:1, 2:3, 3:2, 3:4, 4:3, 4:5, 5:4, 9:16, 16:9 | Output image aspect ratio. Leave empty to preserve the person image's original aspect ratio. | | seed | integer | No | - | 0–2147483647 | Optional seed for deterministic generation with the same inputs. | | output_type | string | No | png | png, jpeg | Desired output image format. | | visual_output_content_moderation | boolean | No | false | - | When enabled, BRIA rejects restricted visual content in the generated output. | ## Example Request ```bash curl -X POST https://api.eachlabs.ai/v1/prediction/ \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "model": "bria-virtual-try-on", "input": { "garment_images": [ "https://cdn-us.eachlabs.ai/defaults/23f20826bbd84c6ea64eb07d5c6b29f3.png" ], "person_image": "https://cdn-us.eachlabs.ai/defaults/a4220a7cde5a4251b1b14ff4de186f48.png" } }' ``` ## Output Schema Response returned by `GET /v1/prediction/{id}` when the job completes: ```json { "status": "success", "predictionID": "string", "output": "string (URL of generated image)", "metrics": { "predict_time": "number (seconds)" } } ``` ## Polling ```bash curl https://api.eachlabs.ai/v1/prediction/{PREDICTION_ID} \ -H "Authorization: Bearer YOUR_API_KEY" ``` | Status | Meaning | |--------|---------| | `processing` | Still running — poll again | | `success` | Done — read `output` | | `error` | Failed — read `message` / `details` | ## Webhook (alternative to polling) Pass `"webhook_url": "https://your.host/path"` in the create request. Eachlabs POSTs this payload when the job ends: ```json { "exec_id": "prediction-uuid", "status": "succeeded", "output": "https://...", "error": "" } ``` `status` is `"succeeded"` or `"failed"`. `exec_id` equals the `predictionID` from create. Return 2xx within 30 seconds. ## Errors Error body: `{ "status": "error", "message": "...", "details": "..." }` | Code | Meaning | |------|---------| | `400` | Invalid input | | `401` | Missing / invalid `Authorization` bearer token | | `404` | Unknown model or prediction id | | `429` | Rate limit — 100 creates / min, 10 concurrent per key | | `5xx` | Retry with backoff | ## Usage Notes - API Base URL: `https://api.eachlabs.ai/v1` - Authentication: send `Authorization: Bearer YOUR_API_KEY`. Generate a key from the Eachlabs dashboard at https://www.eachlabs.ai/dashboard/api-keys. - File-typed parameters (`*_url`, `image_url`, `video_url`, `audio_url`, etc.) accept publicly-reachable HTTPS URLs only. Upload your asset first (GCS / S3 / your CDN) and pass the resulting URL. Data-URIs and localhost URLs are rejected. - For structured parameters (arrays / objects) send real JSON values, not stringified payloads. - Monetary values are reported in USD; per-token / per-megapixel rates may be billed in micro-cents internally. - Prefer `webhook_url` over polling for long-running predictions — see the Webhook Callback section.