Skip to main content
Telara

Integrations / AI21 Labs (direct)

AI21 Labs (direct) logo

AI21 Labs (direct)

TENG-2205: Direct AI21 Labs API calls (Jamba models via the ai21 SDK, no framework) called from customer code. AI21 has no admin or billing API — confirmed against AI21's own docs (docs.ai21.com/docs/usage-cost): usage and billing are visible only under the Studio console (Account > Model usage, Account > Billing & Plans), never through a programmatic endpoint. This connector only receives data if the customer's own code emits an OTel span or log record per chat call carrying the attributes below; an uninstrumented integration reports nothing, not zero. OpenAI-compatibility of AI21's chat API could not be independently confirmed in this research pass (AI21's API-reference subpages were unreachable from this environment); treat it as unconfirmed rather than assumed. There is no telara-observability SDK wrapper for AI21. Instrumentation must be manual: either hand-written OTel spans around the ai21 SDK call site, or — if AI21's endpoint does turn out to be OpenAI-compatible — a generic OpenAI SDK wrapper pointed at AI21's base URL, emitting the gen_ai.* attributes below.

OTLP
Spend

What Telara does

Capability matrix

Indexes NoTracks spend YesDiscovers shadow AI NoRuns actions NoReal-time events No

Before you connect

Prerequisites

A process that uses AI21 Labs (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 AI21 Labs (direct) at it
Enable OpenTelemetry in AI21 Labs (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.