How to Manage Company Resources in the Anthropic API: A Practical Guide

Introduction

If you're using the Claude API as part of a team or organization, you've likely encountered the Company feature in the Anthropic Console. This feature allows you to manage multiple API keys, create isolated workspaces, and control access for different team members or projects. In this guide, we'll walk through everything you need to know to set up and manage your company resources effectively.

What Is the Company Feature?

Anthropic's Company feature is an organizational layer that sits above individual API keys. It allows you to:

• Create multiple workspaces (isolated environments for different projects or teams)
• Generate and manage API keys with specific permissions
• Control billing and usage at the workspace level
• Invite team members with role-based access

Think of it as your team's home base for all Claude API interactions.

Prerequisites

Before diving in, ensure you have:

• An Anthropic account with access to the Console (console.anthropic.com)
• Admin or Owner permissions within the company
• A basic understanding of API keys and REST APIs

Step 1: Accessing Your Company Dashboard

• Log in to console.anthropic.com
• Navigate to the Company section in the left sidebar
• You'll see an overview of your workspaces, API keys, and team members

If you don't see the Company section, you may need to create a company first (available for paid plans).

Step 2: Creating Workspaces

Workspaces allow you to segment your API usage. For example:

• A development workspace for testing
• A production workspace for live applications
• A research workspace for experimentation

To create a workspace:

• Click Create Workspace
• Give it a descriptive name (e.g., "Production - Customer Chatbot")
• (Optional) Add a description
• Click Create

Each workspace gets its own set of API keys and usage quotas.

Step 3: Generating API Keys

Once you have workspaces, you can generate API keys scoped to each workspace.

Using the Console:

• Navigate to the desired workspace
• Click API Keys in the sidebar
• Click Create Key
• Give the key a name (e.g., "Chatbot Backend")
• Select the permissions (Read, Write, or Admin)
• Copy the key immediately — you won't see it again!

Using the API (Programmatic):

You can also create API keys programmatically using the Admin API. Here's an example in Python:

import requests
headers = {
    "x-api-key": "YOUR_ADMIN_API_KEY",
    "anthropic-version": "2023-06-01",
    "Content-Type": "application/json"
}
payload = {
    "name": "Automated Key",
    "workspace_id": "wksp_12345",
    "permissions": ["write"]
}
response = requests.post(
    "https://api.anthropic.com/v1/admin/api_keys",
    headers=headers,
    json=payload
)
print(response.json())

Step 4: Managing Team Members

You can invite team members to your company and assign them to specific workspaces.

Inviting a member:

• Go to Team in the Company dashboard
• Click Invite Member
• Enter their email address
• Select their role:

- Owner: Full access to everything - Admin: Can manage workspaces and keys - Member: Can use assigned workspaces

• Choose which workspaces they can access
• Send the invitation

Step 5: Using Workspace-Specific API Keys in Code

When you make API calls, you'll use the API key generated for that workspace. Here's how to use it in different languages:

Python (using the official SDK):

from anthropic import Anthropic
client = Anthropic(
    api_key="sk-ant-..."  # Your workspace-specific key
)
message = client.messages.create(
    model="claude-3-5-sonnet-20241022",
    max_tokens=1000,
    messages=[
        {"role": "user", "content": "Hello, Claude!"}
    ]
)
print(message.content)

TypeScript (using the official SDK):

import Anthropic from '@anthropic-ai/sdk';
const client = new Anthropic({
  apiKey: 'sk-ant-...'  // Your workspace-specific key
});
async function main() {
  const message = await client.messages.create({
    model: 'claude-3-5-sonnet-20241022',
    max_tokens: 1000,
    messages: [{ role: 'user', content: 'Hello, Claude!' }]
  });
  
  console.log(message.content);
}
main();

Step 6: Monitoring Usage and Billing

Each workspace tracks its own usage. To view:

• Go to Usage in the workspace sidebar
• See token counts, request counts, and costs
• Set usage limits to prevent unexpected bills

You can also set workspace-level spending limits:

import requests
headers = {
    "x-api-key": "YOUR_ADMIN_API_KEY",
    "anthropic-version": "2023-06-01"
}
payload = {
    "workspace_id": "wksp_12345",
    "monthly_limit_usd": 100.00
}
response = requests.post(
    "https://api.anthropic.com/v1/admin/workspaces/limits",
    headers=headers,
    json=payload
)
print(response.json())

Best Practices for Company Management

1. Use Descriptive Names

Name your workspaces and keys clearly. Instead of "Key 1", use "Production Chatbot Key" or "Dev Testing Key".

2. Rotate Keys Regularly

Generate new keys periodically and revoke old ones. This minimizes risk if a key is compromised.

3. Leverage Workspace Isolation

Keep development and production separate. This prevents accidental API calls from breaking your live application.

4. Set Usage Alerts

Configure alerts for when a workspace approaches its spending limit. This helps avoid surprises at the end of the month.

5. Audit Access Regularly

Review who has access to which workspaces. Remove members who no longer need access.

Troubleshooting Common Issues

"API key not found" error

• Ensure you're using the correct key for the workspace
• Check that the key hasn't been revoked
• Verify the key has the necessary permissions

"Workspace not found" when using Admin API

• Double-check the workspace ID (starts with wksp_)
• Ensure your admin key has access to that workspace

Usage not showing up

• It can take up to 5 minutes for usage data to appear
• Check that you're looking at the correct workspace

Conclusion

The Company feature in the Anthropic Console is a powerful tool for teams using the Claude API. By properly setting up workspaces, managing API keys, and controlling access, you can build a secure and scalable infrastructure for your AI applications.

Key Takeaways

• Workspaces provide isolated environments for different projects or teams, each with its own API keys and usage tracking
• API keys should be scoped to specific workspaces and rotated regularly for security
• Team members can be invited with role-based access (Owner, Admin, Member) to specific workspaces
• Usage monitoring at the workspace level helps control costs and prevent unexpected bills
• Programmatic management via the Admin API allows you to automate key creation, workspace setup, and limit configuration