Integrations / Hyperbolic (direct)

Hyperbolic (direct)

Direct Hyperbolic API calls (OpenAI-compatible API via openai SDK, no framework) instrumented by the telara-observability provider wrapper. Spans are tagged telara.span.kind=provider so the cost rollup excludes them when an active framework adapter already covers the same call (double-count guard). Uses the OpenAI SDK with base_url=https://api.hyperbolic.xyz/v1. Hyperbolic has no admin/billing API (console only) — this OTLP path is the only way to attribute spend, since the OpenAIInstrumentor patches the openai SDK client itself regardless of base_url. pip extra: pip install telara-observability[openai]

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 Hyperbolic (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 Hyperbolic (direct) at it

Enable OpenTelemetry in Hyperbolic (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.

input_tokens
tokens
output_tokens
tokens
framework_runs
count

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.