Skip to main content
Telara

Integrations / Windsurf (Codeium)

Windsurf (Codeium) logo

Windsurf (Codeium)

Windsurf (Codeium / Cognition) — User Page Analytics API for per-user activity + prompt-credit usage. Spend connector for the AI Platform Spend Governance feature.

API key
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 Windsurf (Codeium) team.
Team admin access.

Vendor setup

Get the credential

1
Copy the service key
In Windsurf, open Team admin → settings. Copy the Teams Read-only service key.
2
Paste in Telara
Settings → Integrations → Windsurf. Paste it into the service key field Telara shows.

In Telara

Connect in Telara

API key

Windsurf Teams service key with "Teams Read-only" permission (Team admin → settings). NOTE: Windsurf passes the key in the POST BODY (service_key), not an Authorization header.

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

Fields Telara asks for
  • Service 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.

  • active_days
    count
  • prompt_credits_used_cents
    count — Prompt credits used this billing cycle, in cents (cumulative snapshot).

AI estate

What gets discovered

Config paths
  • ~/.codeium/windsurf/mcp_config.json
Resource kinds

mcp_client_configuration, mcp_server_deployment

Config paths
  • .windsurf/mcp_config.json
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

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

Individual editor keys cannot read team usage.
This is not a GitHub or IDE-telemetry connector.