Skip to main content
Telara

Integrations / Claude for Enterprise

Claude for Enterprise logo

Claude for Enterprise

Claude for Enterprise — Compliance API (Activity Feed) + Enterprise Analytics API for per-user / per-workspace usage, cost, and audit governance. Spend-only connector for the AI Platform Spend Governance feature.

API key
Spend
Actions

What Telara does

Capability matrix

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

Before you connect

Prerequisites

A Claude for Work / Enterprise organization.
An org admin who can open Data and privacy.

Vendor setup

Get the credential

1
Open Data and privacy
In claude.ai, open Organization settings → Data and privacy.
2
Create a compliance key
Issue the compliance access key. Member API keys from console.anthropic.com are the wrong class.
3
Paste in Telara
Settings → Integrations → Claude for Enterprise.

In Telara

Connect in Telara

API key

Claude Compliance Access Key (sk-ant-api01-...) created in claude.ai > Organization settings > Data and privacy. The key must carry the `read:compliance_activities` scope at minimum; the Activity Feed endpoint also accepts an Admin API key (sk-ant-admin01-...) with the same scope. The Enterprise Analytics API uses a SEPARATE Analytics API key issued from claude.ai > Analytics > API keys — provision both for full coverage. Auth shape verified at: https://platform.claude.com/docs/en/manage-claude/compliance-api-access

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.

Vendor history: 180 days of vendor-side history.

  • messages_sent
    count
  • prompts_per_user
    count
  • chats_created
    count
  • file_uploads
    count
  • projects_created
    count
  • models_used
    list
  • input_tokens
    tokens
  • output_tokens
    tokens
  • cost_amount_cents
    usd

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

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

Anthropic Console member keys cannot read claude.ai compliance activity.
This is not Anthropic Admin and not Claude Code telemetry.