Bria API vs Google Imagen

Bria API

Per-image prices, 100 free calls without a card, OpenAPI files and Markdown docs make a first call quick, and the terms warrant that customer content is not used for training. Keys are organisation-wide with no scopes, and the API has no changelog or deprecation policy.

Google Imagen

Shutdown dates were published in the Gemini API changelog and the Vertex AI release notes, with replacements named. Discontinued. Calls to imagen model names fail on both the Gemini API and Vertex AI.

Bria API

1. Send the key in the api_token header, not as Authorization: Bearer. Only /v2/image/verify and /v2/video/verify work without it
2. Expect 202 with request_id and status_url from v2 endpoints. Poll GET /v2/status/{request_id} every 1 to 2 seconds, or pass sync: true
3. Status polls count towards the per-endpoint limit (10 a minute on Free, 60 on Pay-as-you-go), so prefer webhook_url for batches
4. Download results promptly. Image URLs expire after 3 days by default, and legacy /v1/product/* results after 1 hour
5. Do not resend a failed POST blindly. There is no idempotency key, and the SDKs retry status polls only

Google Imagen

1. Replace client.models.generate_images with client.models.generate_content and a gemini-3.1-flash-image model
2. Read images from the response content parts, not from generated_images
3. Don't budget from the Vertex Imagen price rows, they describe a retired product
4. If the job needs a mask-based inpaint, use another vendor's fill endpoint, since Gemini image editing is prompt-based