Integrations / Unify (direct)
Unify (direct)
Direct calls to the Unify AI router's OpenAI-compatible API (historically base_url=https://api.unify.ai/v0), instrumented via the OpenAI SDK wrapper — no first-party Unify wrapper exists in telara-observability, but Unify's router was documented as OpenAI-compatible, so the generic OpenAI wrapper pointed at the router's base URL is expected to capture spans the same way it does for other OpenAI-compatible endpoints. pip extra: pip install telara-observability[openai] UNVERIFIED AS OF 2026-08: unify.ai's current public site and docs (docs.unify.ai) present a "virtual AI employee" agent product with no visible LLM-router API reference, and the historical router endpoint (api.unify.ai/v0) now 404s. This connector is written against the previously-documented router shape and should be confirmed against a live Unify account before being marked available to customers — the product may have pivoted away from standalone LLM routing. Unify sits between the customer and the underlying model vendor, so cost attribution here lands on Unify as the router, not on the origin model provider — a real chargeback limitation.
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.
- input_tokenstokens
- output_tokenstokens
- framework_runscount
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

