Keypup reads your Claude usage with an Admin API key of your Claude Console organization. This article explains how to create one.
Create the key in the Claude Console, not in claude.ai. Keys created in claude.ai for a Claude Team or Enterprise plan cannot read the usage reports Keypup imports. See Claude Platform Integration for the plans that are supported.
Prerequisites
You must have the admin role in your Claude Console organization. Owners and primary owners have it too. Only an admin can create an Admin API key.
The Admin API is not available for individual accounts. If your Claude Console account has no organization yet, set one up first under Settings > Organization.
Create the Admin API key
Sign in to the Claude Console and go to Settings > Admin keys.
Click Create key and name it, for example
Keypup.Choose an expiration. When the key expires, the integration disconnects and you need to create a new key, so prefer a long expiration or none.
Click Create and copy the key, which starts with
sk-ant-admin01-. It is only shown once.
Then, in Keypup, go to Settings > App management, click Connect on Claude Platform and paste the key.
Alternative: a personal API key scoped to the organization
If you prefer not to create an Admin API key, an admin can connect with a personal API key instead, provided its scope is the organization rather than a workspace. The scope is shown in the Scope column of Settings > API keys in the Claude Console.
A personal key acts with the permissions of the person who created it, and stops working when that person leaves the organization or loses the admin role, which disconnects the integration. An Admin API key does not depend on one person, which is why we recommend it.
Workspace API keys are rejected: they cannot read the organization's usage.
For more details, see Anthropic's documentation on creating an Admin API key.