Skip to main content

Choose a Claude Code connection

Compare Claude Code connection methods and choose the option that matches your Anthropic environment, data requirements, and collection cadence.

Steven Silverstone
Updated by Steven Silverstone

Overview

LinearB supports three ways to collect Claude Code usage data: Admin API, Analytics API, and OpenTelemetry.

Choose a connection type based on how your organization accesses Claude Code, the credentials available to your administrators, the data you need, and how quickly you need it to appear.

Connection limit: Only one active Claude Code integration using the same connection type can be connected at a time. For example, two Admin API integrations cannot be active simultaneously. A failing integration still counts as active.

Choose a Connection Type

Admin API

Choose Admin API when your organization uses Claude Code through an Anthropic API organization and can provide an admin-level Anthropic API key.

Best for:

  • Detailed Claude Code usage reporting
  • User-level daily attribution
  • Session, tool-action, token, model, and estimated-consumption data
  • Organizations that need historical data backfilled when available

Collection behavior:

  • Data is updated daily.
  • Up to 90 days of historical data can be backfilled during the initial connection.

Configuration guide:


Analytics API

Choose Analytics API when your organization has a Claude Enterprise license and can provide an Anthropic API key with read:analytics access.

Best for:

  • Organization-level Claude usage and adoption summaries
  • User-level usage summaries
  • Claude Enterprise organizations that do not require near-real-time telemetry

Collection behavior:

  • Anthropic documents a three-day delay for Analytics API data.
  • Available analytics data begins from January 1, 2026.
  • This connection is intended for analytics summaries rather than detailed tool-event telemetry.

Configuration guide:


OpenTelemetry

Choose OpenTelemetry to send Claude Code telemetry directly to LinearB using an organization-specific ingest token generated by LinearB.

Best for:

  • Near-real-time Claude Code telemetry
  • Claude Teams environments
  • Claude Code running through AWS Bedrock or another third-party provider
  • Organizations that can deploy Claude managed settings or endpoint configuration

Collection behavior:

  • Data collection begins after OpenTelemetry is enabled and the configuration is deployed.
  • OpenTelemetry does not provide historical backfill.
  • Each developer must approve the managed settings when prompted in their next Claude Code session.

Configuration guide:


Quick Recommendation

  • Use Admin API for detailed daily reporting from an Anthropic API organization.
  • Use Analytics API for Claude Enterprise usage and adoption summaries.
  • Use OpenTelemetry for the most immediate telemetry or when Claude Code runs through AWS Bedrock or another third-party provider.

Add a Claude Code Integration

  1. Go to Settings → Company Settings → AI Tools → Integrations.
  2. Click Add New.
  3. Select Claude Code and click Continue.
  4. Select Admin API, Analytics API, or OpenTelemetry.
  5. Click Continue.
  6. Enter the credentials and configuration required for the selected connection type.
  7. Click Connect.

LinearB validates the submitted configuration. When validation succeeds, the integration appears under Connected.

Duplicate integrations: If an active integration already uses the same Claude Code connection type, disconnect it before connecting another integration of that type.

Manage a Claude Code Integration

The following actions are available:

  • Connect — create and activate a new Claude Code integration.
  • Edit — update the available settings for a connected Admin API or Analytics API integration.
  • Disconnect — stop new data collection and move the integration to the Disconnected list.
  • Reconnect — validate and reactivate a previously disconnected integration.

Edit an Admin API or Analytics API integration

  1. Open Settings → Company Settings → AI Tools → Integrations.
  2. Select Connected.
  3. Select the Claude Code integration you want to update.
  4. Under Main Settings, click Edit.
  5. Update the Anthropic API key.
  6. Click Save changes to apply the update or Cancel to discard it.
Important: You cannot change the connection type through Edit mode. To use another collection method, add a new Claude Code integration with the required connection type.

What happens to historical data?

Editing an Admin API or Analytics API integration does not delete previously collected metrics.

  • Saving an API-key change triggers a new collection.
  • LinearB can recollect up to 90 days of recent Claude Code data.
  • Recollected records are updated in place and are not counted twice.
  • Data older than the recollection window remains unchanged.

Rotate an OpenTelemetry token

Claude Code OpenTelemetry does not provide an Edit action. If its ingest token must be replaced, use the token-rotation action in the integration details.

Important: After rotating the token, update the deployed OpenTelemetry configuration. Data stops arriving until the new token is deployed, and data from that interruption is not backfilled.

Learn more:


Where Claude Code Data Appears

Adoption and accepted-lines data appears in AI Analytics.

When supported by the selected connection, model, token, and estimated-consumption data is available through Metrics Builder.

Estimated consumption is not a billing total. Vendor plans, discounts, credits, negotiated pricing, and pricing changes can cause the estimate to differ from the provider’s invoice.

How did we do?

Manage AI tool integrations

Choose a GitHub Copilot connection

Contact