Skip to main content
Telara

Integrations / Segmind (direct)

Segmind (direct) logo

Segmind (direct)

Segmind multi-model image/video generation API (api.segmind.com; hundreds of model endpoints — SDXL, Flux, video and upscaling pipelines, etc.) called directly from customer code. TENG-2205: no telara-observability SDK wrapper exists for Segmind, and there is no OpenAI-compatible fallback — each Segmind model is its own REST endpoint with a model-specific request/response shape, not a chat completion. This connector only receives data if the customer's own code emits an OTel span or log record per inference call carrying the attributes below; an uninstrumented integration reports nothing, not zero. Segmind meters usage in "billing units" (Segmind's own per-model credit system — the unit cost differs per model/pipeline and per output resolution), not tokens, so gen_ai.usage.* attributes do not apply and are intentionally absent. There is no admin/billing API exposing balance or per-call unit cost outside the account dashboard, which is why this is otlp_push rather than a pull connector. Cost is NOT derived to USD: Segmind's billing-unit rate varies per model and is not published as a single stable table, so no model_price_table is set. This connector reports billing-unit and call counts only; $ appears only if the customer's own code emits a cost_usd attribute.

OTLP
Spend

What Telara does

Capability matrix

Before you connect

Prerequisites

A process that uses Segmind (direct) and can export OpenTelemetry.
Ability to run the Telara CLI where that process runs.

Vendor setup

Get the credential

1
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.
2
Point Segmind (direct) at it
Enable OpenTelemetry in Segmind (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.

  • billing_units
    count — Segmind "billing units" consumed by this call — Segmind's own opaque credit unit, priced per model/pipeline and output resolution rather than a fixed rate. Not returned on the response body; the customer's instrumentation must read it from the dashboard-reported per-model rate and set it explicitly, or this metric reads zero for that span.
  • model
    count — Count of calls per Segmind model/pipeline slug invoked (e.g. sdxl1.0-txt2img, flux-1-dev).
  • generations
    count — Count of inference calls (one span/log per request), across all Segmind model endpoints.

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.