Skip to main content
Telara

Integrations / Tabnine

Tabnine logo

Tabnine

Tabnine Enterprise — admin Usage Metrics API for per-user, per-model token + cost across code completions, chat, agent, and instruct. Spend connector for the AI Platform Spend Governance feature.

API key
Spend

What Telara does

Capability matrix

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

Before you connect

Prerequisites

A Tabnine Enterprise organization. Starter and Pro do not expose organization usage APIs.
Enterprise admin who can open Settings → Access Tokens.

Vendor setup

Get the credential

1
Open Access Tokens
Sign in to the Tabnine Enterprise console. Open Settings → Access Tokens.
2
Create a token
Click Create. Name it for Telara. Set an expiry your policy allows. Copy the token once. This token authorizes organization, team, and user usage endpoints.
3
Paste in Telara
Settings → Integrations → Tabnine. Paste the admin access token.

In Telara

Connect in Telara

API key

Tabnine Enterprise admin access token (Settings → Access Tokens, configurable expiry). Enterprise plan only. The token authorizes the /organization, /team, and /user usage endpoints.

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

Fields Telara asks for
  • API key

Spend

What gets measured

Resolution: Aggregated buckets.

Attribution: Matched to people by the vendor user id.

How far back vendor history goes is not published uniformly for this connector.

  • active_users
    users
  • code_completions
    count
  • lines_completed
    lines
  • chat_messages
    count
  • chat_input_tokens
    tokens
  • chat_output_tokens
    tokens
  • agent_input_tokens
    tokens
  • agent_output_tokens
    tokens

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 personal IDE token cannot read organization usage.
Tokens expire. When usage stops, issue a new access token in the same Settings page.