Integrations / Anthropic SDK (direct)

Anthropic SDK (direct)

Direct Anthropic SDK calls (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).

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

An application (or worker) that calls Anthropic through the official SDK 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 an Anthropic API key on this connector.

Export from the SDK

Point the Anthropic SDK’s OpenTelemetry exporter (or your collector) at that endpoint.

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

Usage only arrives for processes you instrument. Console keys and org spend belong on Anthropic Admin.

A missing exporter is the usual empty chart — the SDK call succeeded, telemetry never left the process.