Integrations / Civitai (direct)

Civitai (direct)

Civitai image-generation API (civitai.com — community model hub with a generation API for its hosted Stable Diffusion / Flux-family models) called directly from customer code. TENG-2205: no telara-observability SDK wrapper exists for Civitai, and there is no OpenAI-compatible fallback — Civitai's generation endpoints take model/workflow-specific parameters, not a chat-completion shape. This connector only receives data if the customer's own code emits an OTel span or log record per generate call carrying the attributes below; an uninstrumented integration reports nothing, not zero. Civitai meters usage in "Buzz" — its own platform credit, consumed per generation at a rate that varies by model and resolution. Civitai already offers a native OAuth (authorization code + PKCE) app model with per-app Buzz spend caps enforced platform-side, so for OAuth-integrated apps Civitai itself is the primary spend control; this OTLP connector is a customer-side, per-user usage view on top of that — not a replacement for it. There is no admin/billing API exposing historical Buzz consumption by user, which is why this is otlp_push rather than a pull connector. Cost is NOT derived to USD: Buzz is sold in bundles at a blended rate that varies by purchase tier and is not a stable public $/Buzz figure, so no model_price_table is set. This connector reports Buzz-credit and call counts only; $ appears only if the customer's own code emits a cost_usd attribute.

OTLP

Spend

What Telara does

Capability matrix

Indexes No Tracks spend Yes Discovers shadow AI No Runs actions No Real-time events No

Before you connect

Prerequisites

A process that uses Civitai (direct) and can export OpenTelemetry.

Ability to run the Telara CLI where that process runs.

Vendor setup

Get the credential

Print the OTLP endpoint

Run `telara otlp`. It prints the endpoint and headers Telara expects. Do not paste a vendor API key on this connector.

Point Civitai (direct) at it

Enable OpenTelemetry in Civitai (direct) (or in your collector) and send traces to the endpoint that command prints.

In Telara

Connect in Telara

OTLP

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.

buzz_credits
count — Buzz credits consumed by this generation call — Civitai's own billable unit, priced per model/resolution. Not guaranteed on the response body for every workflow; the customer's instrumentation must set it explicitly (e.g. from the job-cost field Civitai returns for generation jobs), or this metric reads zero for that span.
images
count — Number of images returned by the generation job.
generations
count — Count of generation calls (one span/log per job submitted).

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

Known limitations

Nothing appears in Telara until that process actually emits telemetry.

This is not an admin-key connector. Org-level spend, if Telara offers it for this vendor, is a separate page.