Skip to main content

Anthropic

Visualize Anthropic organization data in the JupiterOne graph. Map users to workspaces, track API key ownership and status, and monitor identity and access changes through custom queries and alerts.

Installation

The Anthropic integration ingests organization details, users, workspaces, workspace memberships, and API keys using the Anthropic Admin API. Before setting up the integration in JupiterOne, you will need to create an Admin API key in the Claude Console.

Prerequisites

  • An Anthropic organization (the Admin API is unavailable for individual accounts). If you have not set one up, go to Console > Settings > Organization first.
  • An organization member with the admin role — only admins can create Admin API keys.
  • Access to JupiterOne with permission to configure integrations.

Creating an Admin API key in Anthropic

  1. Log in to the Claude Console as an organization admin.
  2. Navigate to Settings > Admin Keys (https://platform.claude.com/settings/admin-keys).
  3. Click Create Admin Key and give it a recognizable name (for example, JupiterOne Integration).
  4. Copy the generated key — it starts with sk-ant-admin and is shown only once.
note

Admin API keys are separate from standard API keys. Only organization admins can create them, and they provide access to the organization management endpoints (/v1/organizations/me, /v1/organizations/users, /v1/organizations/workspaces, workspace members, and /v1/organizations/api_keys). No additional scope configuration is required — the integration only reads from these endpoints.

Configuration in JupiterOne

To install the Anthropic integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select Anthropic. Click New Instance to begin configuring your integration.

Creating an instance requires the following:

  • The Account Name used to identify the Anthropic account in JupiterOne. Ingested entities will have this value stored in tag.AccountName when the AccountName toggle is enabled.

  • Description to assist in identifying the integration instance, if desired.

  • Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as DISABLED and manually execute the integration.

  • Your Anthropic API Key — the Admin API key created above (starts with sk-ant-admin). This field is required.

  • Optionally, a Base URL to override the Anthropic API endpoint. Leave blank to use the default https://api.anthropic.com.

  • Optionally, an Anthropic Version to override the anthropic-version request header. Leave blank to use the default 2023-06-01.

Click Create once all values are provided to finalize the integration.

Next steps

Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.