Skip to main content
Telara

Integrations / Sourcegraph Cody

Sourcegraph Cody logo

Sourcegraph Cody

Sourcegraph Cody / Amp — Analytics API (CSV) for per-user-per-day code AI usage (searches, chats, autocomplete, CAR%). Spend connector for the AI Platform Spend Governance feature.

OAuth 2.0
Spend
AI estate

What Telara does

Capability matrix

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

Before you connect

Prerequisites

A Sourcegraph Enterprise instance with Cody. Cody Free / Pro on sourcegraph.com does not expose this analytics token.
Site admin who can open analytics.sourcegraph.com (or the instance’s analytics) and create access tokens.

Vendor setup

Get the credential

1
Open Access Tokens
Sign in to Sourcegraph Analytics (analytics.sourcegraph.com, or the analytics entry on your instance). Open Access Tokens.
2
Create a token
Click Create access token. Name it for Telara. Copy it. Sourcegraph authorizes with a token prefix on the Authorization header — Telara’s form handles that.
3
Paste in Telara
Settings → Integrations → Sourcegraph Cody. Paste the analytics access token.

Permissions Telara requests

  • mcp
    OAuth 2.0

In Telara

Connect in Telara

OAuth 2.0

Per-instance Sourcegraph OAuth metadata for MCP dynamic client registration. DCR clients are restricted to mcp; prove the issued token is accepted by the selected Sourcegraph API surface before enabling browser authorization.

In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.

API key

Sourcegraph Analytics access token (analytics.sourcegraph.com → Access Tokens). Enterprise. The token authorizes the by-user-client-date report. Sourcegraph uses `Authorization: token <key>`.

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: Per user per day.

Attribution: Matched to people by email.

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

  • searches
    count
  • chat_events
    count
  • completions_suggested
    count
  • completions_accepted
    count
  • chars_written
    count

AI estate

What gets discovered

Config paths
  • ~/.config/amp/settings.json
  • ~/.config/amp/settings.jsonc
Resource kinds

mcp_client_configuration, mcp_server_deployment

Config paths
  • .amp/settings.json
  • .amp/settings.jsonc
Resource kinds

mcp_client_configuration, mcp_server_deployment

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

The scopes above are the permissions this connector requests. They come from the catalog, not from a hand-written page.

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

An instance access token from user settings is the wrong class if Telara asks for an analytics token.
Cody usage only appears after analytics is enabled for the instance.