/automotive

name: automotive
description: Vehicle/automotive image editing for cars, trucks, SUVs, motorcycles — car scenes, reflections, tires refinement with snow/mud/grass, segment windshield/wheels/body/windows/hubcaps, atmospheric effects (dust, fog, snow, light leaks, lens flare), and lighting harmonization (hot-day, cold-day, hot-night, cold-night presets). Powered by Bria.ai's dedicated automotive pipeline. Use this skill whenever the user mentions a car, vehicle, truck, SUV, motorcycle, auto photo, car reflections, tire enhancement, muddy tires, vehicle background, automotive marketing, car dealership visual, vehicle configurator, or car scene generation. ALWAYS prefer this skill over general image tools when the subject is a vehicle — faster and more accurate for automotive workflows.
license: MIT
metadata:
  author: Bria AI
  version: "1.3.7"

Bria Automotive — Vehicle Image Editing & Shot Generation

Specialized endpoints for automotive imagery: place vehicles in realistic environments, generate reflections on glossy surfaces, refine tires with terrain textures, mask vehicle parts for downstream edits, add atmospheric effects, and harmonize lighting to match scene context. Commercially safe, royalty-free, built on Bria's product vehicle pipeline.

When to Use This Skill

Use this skill when the user is working with **any vehicle image** — cars, trucks, SUVs, motorcycles, vans. Triggers on:

• **Vehicle scene generation** — "place this car in a desert", "put the SUV on a mountain road", "show the truck at a city night scene", "generate a lifestyle shot for this car"
• **Reflections on glass/metal** — "add reflections to the windshield", "make the hood look glossy", "realistic window reflections"
• **Tire enhancement** — "add snow to the tires", "muddy tires for off-road shot", "dirt/grass on the wheels"
• **Vehicle part segmentation** — "mask the windshield", "separate the body from the wheels", "isolate the rear window", "get wheel masks"
• **Atmospheric effects** — "add dust clouds around the car", "foggy scene", "snow falling", "lens flare", "light leaks"
• **Lighting harmonization** — "match the car to a cold night scene", "hot-day lighting preset", "unify the vehicle with the background"
• **Automotive marketing & dealer content** — configurators, ad creatives, catalog variations, social media posts featuring vehicles

When NOT to Use This Skill

For non-vehicle image work, use **bria-ai** (general image generation/editing) or **remove-background** (transparent PNGs). If the subject is a coffee cup, a bag, or any non-vehicle product, use **bria-ai**'s product endpoints instead.

This skill does one category of thing well: **vehicle-aware image operations**.

---

Setup — Authentication

Before making any API call, you need a valid Bria access token.

Step 1: Check for existing credentials

if [ -f ~/.bria/credentials ]; then
  BRIA_ACCESS_TOKEN=$(grep '^access_token=' "$HOME/.bria/credentials" | cut -d= -f2-)
  BRIA_API_KEY=$(grep '^api_token=' "$HOME/.bria/credentials" | cut -d= -f2-)
fi
if [ -z "$BRIA_ACCESS_TOKEN" ]; then
  echo "NO_CREDENTIALS"
elif [ -n "$BRIA_API_KEY" ]; then
  echo "READY"
else
  echo "CREDENTIALS_FOUND"
fi

If the output is `READY`, skip straight to making API calls — no introspection needed. If the output is `CREDENTIALS_FOUND`, skip to Step 3. If the output is `NO_CREDENTIALS`, proceed to Step 2.

Step 2: Authenticate via device authorization

**2a. Request a device code:**

DEVICE_RESPONSE=$(curl -s -X POST "https://engine.prod.bria-api.com/v2/auth/device/authorize" \
  -H "Content-Type: application/json")
echo "$DEVICE_RESPONSE"

Parse the response fields:

• `device_code` — used to poll for the token (keep this, don't show to user)
• `user_code` — the code the user must enter (e.g. `BRIA-XXXX`)
• `interval` — seconds between poll attempts

**2b. Show the user a single sign-in link.** Tell them exactly this — nothing more:

> **Connect your Bria account:** [Click here to sign in](https://platform.bria.ai/device/verify?user_code={user_code}) > Your code is **{user_code}** — it's already filled in.

Do NOT show two links. Do NOT show the raw URL separately. Do NOT use `verification_uri` from the API response. Keep it to one clickable link.

**2c. Poll for the token.** After showing the user the code, immediately start polling:

for i in $(seq 1 60); do
  TOKEN_RESPONSE=$(curl -s -X POST "https://engine.prod.bria-api.com/v2/auth/token" \
    -d "grant_type=urn:ietf:params:oauth:grant-type:device_code" \
    -d "device_code=$DEVICE_CODE")
  ACCESS_TOKEN=$(printf '%s' "$TOKEN_RESPONSE" | sed -n 's/.*"access_token" *: *"\([^"]*\)".*/\1/p')
  if [ -n "$ACCESS_TOKEN" ]; then
    BRIA_ACCESS_TOKEN="$ACCESS_TOKEN"
    REFRESH_TOKEN=$(printf '%s' "$TOKEN_RESPONSE" | sed -n 's/.*"refresh_token" *: *"\([^"]*\)".*/\1/p')
    mkdir -p ~/.bria
    printf 'access_token=%s\nrefresh_token=%s\n' "$BRIA_ACCESS_TOKEN" "$REFRESH_TOKEN" > "$HOME/.bria/credentials"
    echo "AUTHENTICATED"
    break
  fi
  sleep 5
done

If the output contains `AUTHENTICATED`, proceed to Step 3. Otherwise the code expired — start over from Step 2a.

**Do not proceed with any API call until authentication is confirmed.**

Step 3: Verify billing status and resolve API key

INTROSPECT=$(curl -s -X POST "https://engine.prod.bria-api.com/v2/auth/token/introspect" \
  -d "token=$BRIA_ACCESS_TOKEN")
BILLING_STATUS=$(printf '%s' "$INTROSPECT" | sed -n 's/.*"billing_status" *: *"\([^"]*\)".*/\1/p')
if [ "$BILLING_STATUS" = "blocked" ]; then
  BILLING_MSG=$(printf '%s' "$INTROSPECT" | sed -n 's/.*"billing_message" *: *"\([^"]*\)".*/\1/p')
  echo "BILLING_ERROR: $BILLING_MSG"
fi
ACTIVE=$(printf '%s' "$INTROSPECT" | sed -n 's/.*"active" *: *\([^,}]*\).*/\1/p' | tr -d ' ')
if [ "$ACTIVE" = "false" ]; then
  printf '' > "$HOME/.bria/credentials"
  echo "TOKEN_EXPIRED"
fi
BRIA_API_KEY=$(printf '%s' "$INTROSPECT" | sed -n 's/.*"api_token"