Skip to main content
Cortex connects to many third-party vendors whose system interfaces frequently change. As a result, integration behavior or configuration steps may shift without notice. If you encounter unexpected issues, check with your system administrator or refer to the vendor’s documentation for the most current information. Additionally, integration sync times vary and are subject to scheduling overrides and timing variance.

Why use the integration for Claude

Claude Code is Anthropic’s artificial intelligence (AI) coding tool. Integrating Cortex with Claude brings your organization’s Claude Code usage into Eng Intelligence, so you can see what the tool costs, who uses it, and how that use relates to delivery. With the Claude integration, Cortex can:
  • Show Claude Code spend, token usage, and spend by model in the AI Dashboard.
  • Track Claude Code adoption across your developers and teams, alongside GitHub Copilot.
  • Compare delivery metrics, such as cycle time and pull request (PR) size, between developers who use Claude Code and developers who don’t.
Cortex connects to Claude with an application programming interface (API) key and only reads Claude Code usage data. The integration doesn’t include other API calls, and it doesn’t include developers who sign in to Claude Code with a claude.ai Team or Pro seat.

Configuring Claude

There are two ways to connect Claude to Cortex, depending on the subscription your organization uses:
  • Enterprise - For seat-based plans managed at claude.ai. Cortex connects with an API key from your Claude Enterprise organization.
  • Console - For API usage billed through the Claude Console. Cortex connects with an Admin API key.

Prerequisites

  • Users with the Configure Integrations permission can configure Claude.
  • An API key, created in your Claude Enterprise organization or in the Claude Console.

Step 1: Creating an API key in Claude

Follow the steps for the subscription your organization uses. Enterprise
  1. In your Claude Enterprise organization, go to Org settings > API.
  2. Create an API key with both the read:analytics and read:members scopes.
  3. Copy the key and store it in a secure location.
Scopes are fixed when you create the key. To add a scope later, you must create a new key.
Console
  1. In the Claude Console, go to Settings > Admin keys.
  2. Create an Admin API key. One key covers one Anthropic organization.
  3. Copy the key and store it in a secure location.
Console admin keys are unscoped. The key grants full Admin API access to your Anthropic organization, including members, workspaces, and API keys. Cortex uses it only to read Claude Code usage data.

Step 2: Configuring the integration in Cortex

  1. From the main sidebar, expand Integrations, then select Configurations.
  2. Search for Claude, then click Install. The Claude side panel opens.
  3. Select Enterprise or Console.
  4. In the Claude side panel, do the following:
    1. From the Category dropdown, leave AI Tools selected.
    2. Under Configuration alias, enter an alias for this configuration.
    3. Under API key, paste the API key you created in step 1.
    4. Click Test connection. A successful connection means your integration is configured correctly.
    5. Click Save.
If you have more than one Anthropic organization, repeat these steps to add a configuration for each one.
To modify an existing configuration, see Modifying an integration configuration.

Using the integration

After you save a configuration, Claude Code data appears in the AI Dashboard. For details, see Claude Code in the AI Dashboard. The Spend tab only appears when a Console or Enterprise configuration exists. To attribute usage to teams, set up teams and identity mappings in Cortex. The Claude integration doesn’t import entities into Cortex, and you don’t need to connect entities to it.

Viewing Claude integration logs

This feature is available in Cortex cloud.
While viewing an integration’s settings page, select the Error logs tab to view errors from the last 7 days. You can filter the logs list by configuration and by operation (for example, you could filter to view errors surfaced only via Scorecards).
The 'Logs' tab on an integration's settings page shows error information over the past 7 days.
Click into a row to get more information, including time stamp, status code, full error, and request path.
Last modified on November 13, 2026