How to Manage Your Anthropic Account and API Keys: A Complete Guide for Claude Users

Introduction

If you're using Claude AI through the API—whether for a personal project, a startup, or an enterprise deployment—you need to understand how to manage your Anthropic account effectively. The "Company" section of the Anthropic Console is your command center for API keys, billing, team management, and usage monitoring.

This guide covers everything you need to know to set up and maintain your Anthropic company account, keep your API keys secure, and avoid unexpected bills.

What Is the Anthropic Console?

The Anthropic Console is the web-based dashboard where you manage your Claude API usage. After signing up, you'll see a left-hand navigation menu with sections including:

• Dashboard – Overview of API usage and costs
• API Keys – Create and manage authentication tokens
• Settings – Account preferences and notification settings
• Billing – Payment methods, usage limits, and invoices
• Team – Invite members and manage permissions
• Logs – View API request history

The Company settings (sometimes labeled as your organization name) control the top-level account that owns all projects and billing.

Step 1: Creating Your Company Account

When you first sign up for the Anthropic API, you'll be prompted to create a company (or organization). This is the billing entity.

What You'll Need:

• A valid email address
• A company name (can be your personal name for individual use)
• Payment information (credit card or billing details)

How to Do It:

• Go to console.anthropic.com
• Click Sign Up and follow the email verification process
• After logging in, you'll be asked to create an organization
• Enter your company name and billing details
• Confirm your plan (Pay-as-you-go is the default)

Tip: If you're a solo developer, you can name your organization "[Your Name] Personal" to keep things simple.

Step 2: Generating and Managing API Keys

API keys are how your applications authenticate with Claude. Each key is a secret token that grants access to the API.

Creating a New API Key

• In the Console, click API Keys in the left sidebar
• Click the Create Key button
• Give your key a descriptive name (e.g., "Production App", "Dev Testing")
• Optionally, set a usage limit for this specific key (see Step 3)
• Click Create

Important: Copy the key immediately! Anthropic will not show it again. Store it securely in a password manager or environment variable.

Example: Using Your API Key in Python

import anthropic
client = anthropic.Anthropic(
    api_key="sk-ant-..."  # Replace with your actual key
)
message = client.messages.create(
    model="claude-sonnet-4-20250514",
    max_tokens=1000,
    messages=[
        {"role": "user", "content": "Hello, Claude!"}
    ]
)
print(message.content)

Best Practices for API Key Security

• Never hardcode keys in source code or commit them to Git
• Use environment variables or a secrets manager
• Rotate keys regularly (every 90 days recommended)
• Use separate keys for development, staging, and production
• Delete unused keys immediately

Rotating an API Key

• Go to API Keys in the Console
• Find the key you want to rotate
• Click the three dots (⋮) and select Revoke
• Create a new key following the steps above
• Update your application with the new key

Step 3: Setting Usage Limits and Budget Controls

One of the most important features in the Company settings is usage limits. Without them, a runaway script could generate unexpected charges.

Setting an Organization-Wide Spending Limit

• Go to Billing > Usage Limits
• Enable Hard Limit – this stops API calls once the limit is reached
• Set your monthly budget (e.g., $100)
• Optionally, set a Soft Limit to receive email alerts at 50%, 80%, and 90% of your budget

Setting Per-Key Usage Limits

When creating or editing an API key, you can assign a rate limit (requests per minute) and a monthly spending cap. This is useful for:

• Limiting a development key to $10/month
• Capping a key used by a junior developer
• Preventing a misconfigured integration from draining your account

Step 4: Managing Team Members

If you're working with a team, you can invite members to your Anthropic organization.

Inviting a Team Member

• Go to Team in the left sidebar
• Click Invite Member
• Enter their email address
• Choose a role:

- Admin – Full access to billing, keys, and settings - Developer – Can create and use API keys, view logs, but cannot change billing - Viewer – Read-only access to usage and logs

• Click Send Invite

Managing Permissions

Each team member can have their own API keys, making it easy to track individual usage. Admins can revoke any key at any time.

Step 5: Monitoring Usage and Billing

Viewing Real-Time Usage

• Go to Dashboard to see:

- Total tokens used (input + output) - Cost breakdown by model (e.g., Claude Sonnet vs. Claude Haiku) - Requests per minute (RPM) and tokens per minute (TPM)

Exporting Usage Data

You can download CSV reports from the Logs section for detailed analysis. This is helpful for:

• Chargebacks to internal teams
• Identifying unusual spikes in usage
• Forecasting future costs

Setting Up Billing Alerts

Under Billing > Notifications, you can configure email alerts for:

• When spending reaches a certain percentage of your limit
• When a new invoice is generated
• When payment fails

Troubleshooting Common Account Issues

"API Key Not Found" Error

If you get a 401 error, your API key may be:

• Expired or revoked
• Copied incorrectly (check for extra spaces)
• From a different organization

Fix: Generate a new key and update your application.

Unexpected Charges

• Check Dashboard for usage spikes
• Review Logs to identify which application or user caused the increase
• Set a hard limit immediately
• Consider rotating all keys if you suspect a leak

Cannot Invite Team Members

Only Admins can invite members. If you're a Developer or Viewer, ask your organization admin to upgrade your role.

Conclusion

Managing your Anthropic company account doesn't have to be complicated. By following the steps in this guide, you can:

• Create and secure API keys
• Control costs with usage limits
• Collaborate with your team safely
• Monitor usage in real time

Take a few minutes today to set up your billing alerts and rotate any old API keys. Your future self (and your wallet) will thank you.

Key Takeaways

• Always use environment variables for API keys—never hardcode them in your source code.
• Set hard spending limits in the Billing section to prevent runaway costs from bugs or misuse.
• Rotate API keys regularly (every 90 days) and revoke keys that are no longer in use.
• Use separate keys for different environments (dev, staging, production) to isolate issues and control access.
• Monitor your Dashboard weekly to catch unexpected usage patterns early.