Integrations / Bria (direct)
Bria (direct)
Bria enterprise/IP-safe visual generation API (docs.bria.ai — image generation, background removal, image/video editing endpoints, trained on licensed data) called directly from customer code. TENG-2205: no telara-observability SDK wrapper exists for Bria, and there is no OpenAI-compatible fallback — Bria exposes several distinct operation types (generate, background-remove, video-edit, ...) with their own request/ response shapes, not a single chat-completion call. This connector only receives data if the customer's own code emits an OTel span or log record per operation call carrying the attributes below; an uninstrumented integration reports nothing, not zero. Bria does NOT bill in credits — its public pay-as-you-go pricing is a fixed $ rate per operation (e.g. ~$0.03/image generated, ~$0.018/ background removal, ~$0.0225-0.045/second for video edits), but the rate differs by operation type and there is no admin/billing API to confirm which rate applied to a given call, which is why this is otlp_push rather than a pull connector. Cost is NOT derived to USD here: because the per-unit rate depends on which of several operation types was called and Bria exposes no reliable operation-type tag on the response, hardcoding a single model_price_table would silently misprice a subset of calls — worse than no dollar figure. This connector reports operation and video-second counts only; $ appears only if the customer's own code computes and emits a cost_usd attribute using its own knowledge of which endpoint it called.
What Telara does
Capability matrix
Before you connect
Prerequisites
Vendor setup
Get the credential
In Telara
Connect in Telara
This connector does not take a vendor key in Settings → Integrations. Run `telara otlp` (or point the vendor’s OpenTelemetry exporter at the endpoint that command prints) so usage arrives as telemetry.
Telara has not published the exact form fields for this method yet. Complete whatever the Connect dialog shows.
Spend
What gets measured
Resolution: Per request.
Attribution: Matched to people by email.
How far back vendor history goes is not published uniformly for this connector.
- generationscount — Count of Bria API operations (generate, background-remove, video-edit, ...). One span/log per call; the customer's instrumentation should set bria.operation to the endpoint name so this count can be broken out by operation type downstream.
- imagescount — Number of output images produced, for image-shaped operations (generate, background-remove). Zero/absent on video-only calls.
- video_secondsseconds — Seconds of video processed, for video-edit operations (Bria's video endpoints bill per second). Legitimately zero/absent on image-only calls — this is a partial-coverage metric by design, not an always-zero placeholder.
Sync
Freshness & sync
Spend connectors refresh on the vendor pull cadence declared in the catalog. Indexing lag is not published for this connector.
Data handling
Permissions & data handling
Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.
This catalog entry does not declare extra semantic-search exclusions.
After connect
Verify it worked
This connector does not declare a credential probe yet. A saved connection means Telara stored the credential, not that the vendor accepted it.
Honesty

