Integrations / LiteLLM Proxy

LiteLLM Proxy

Self-hosted LiteLLM Proxy spend tracking — pulls /spend/logs for per-request cost, tokens, and user_id attribution. Customers set the proxy base URL as tenant config; Telara never embeds a LiteLLM instance.

API key

Spend

Actions

What Telara does

Capability matrix

Indexes No Tracks spend Yes Discovers shadow AI No Runs actions Yes Real-time events No

Before you connect

Prerequisites

A LiteLLM Proxy Telara can reach.

The proxy master key, or a key that can read spend.

Vendor setup

Get the credential

Copy the proxy URL and key

From your LiteLLM Proxy deploy, copy the base URL people use to reach the proxy and the master key (or a spend-read key).

Paste in Telara

Settings → Integrations → LiteLLM Proxy.

In Telara

Connect in Telara

API key

LiteLLM Proxy master key (or a key with spend-read scope) and the proxy base URL (e.g. https://litellm.internal.example.com).

In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.

Fields Telara asks for

API key
Base Url

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
requests
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

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

Honesty

Known limitations

A virtual key that can only complete prompts may not read spend.

This is not the LiteLLM webhook connector, and not SDK telemetry.