Integrations / Devin

Devin

Devin (Cognition) autonomous software engineer — Consumption API for per-session ACU usage, outcomes, and org usage metrics. Spend-only connector for the AI Platform Spend Governance feature.

API key

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

A Devin organization (Cognition) you can administer.

Org admin who can open Settings → Service users.

Vendor setup

Get the credential

Open Service users

Create a service user key

Create a service user for Telara. Issue an organization-scoped API key (Devin shows a cog_ prefix). Copy the key and the org id from the same Settings page. Grant the metric permissions this page lists from the catalog.

Paste in Telara

Settings → Integrations → Devin. Paste the key and org id.

In Telara

Connect in Telara

API key

Devin organization-scoped service user API key (cog_ prefix) and org id from Settings → Service users. The key needs ViewAccountMetrics for organization metrics and ViewOrgSessions for per-session rows.

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

Fields Telara asks for

API key
Org Id

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.

total_sessions
count
total_searches
count
total_prs_created
count
total_prs_merged
count
sessions_created
count
avg_acus_per_session
count
sessions_with_merged_prs
count
acus_consumed
count — Agentic Compute Units consumed by the session (~15 min autonomous work = 1 ACU). The billable usage unit.
devin_sessions
count
prs_created
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 personal member key is the wrong class. Telara needs the organization service-user key.

Keys that cannot read account metrics connect and then show no ACU usage.