How to Manage Your Anthropic Account and API Keys: A Complete Guide
Learn how to navigate the Anthropic Console to manage your company account, create and rotate API keys, set usage limits, and monitor billing for Claude API access.
This guide walks you through setting up and managing your Anthropic company account, including creating API keys, configuring billing alerts, and monitoring usage to keep your Claude API integration running smoothly.
Introduction
If you're building with Claude via the API, your Anthropic Console account is your command center. It's where you manage API keys, track usage, set spending limits, and handle billing. Whether you're a solo developer or part of a team, understanding how to navigate the Company settings in the Anthropic Console is essential for keeping your projects secure and your costs under control.
This guide covers everything you need to know about managing your Anthropic account, from creating your first API key to setting up usage alerts and managing team members.
What Is the Anthropic Console?
The Anthropic Console (console.anthropic.com) is the web-based dashboard for managing your Claude API access. When you sign up, you create a Company account. This is the top-level organizational entity that holds your API keys, billing information, and usage data.
Key features of the Console include:
- API Key management – Create, list, and revoke keys
- Usage monitoring – View real-time token consumption and costs
- Billing – Set spending limits, view invoices, and manage payment methods
- Team management – Add or remove users (for organizations)
Step 1: Creating Your Account and Company
Before you can use the Claude API, you need an Anthropic account.
- Go to console.anthropic.com
- Click Sign Up and complete the registration (email + password or Google/GitHub OAuth)
- After verifying your email, you'll be prompted to create a Company. This is your account's organizational name (e.g., "Acme Corp" or your personal name)
- Fill in your company details and accept the terms of service
Note: Your Company name is visible on invoices and billing statements. Choose something recognizable.
Once your Company is created, you'll land on the Console dashboard. This is your home base for all account management.
Step 2: Generating Your First API Key
API keys are how your applications authenticate with Claude. Each key is tied to your Company account and inherits its billing and rate limits.
How to Create an API Key
- In the Console sidebar, click API Keys
- Click the Create Key button
- Give your key a descriptive name (e.g., "Production App", "Dev Testing")
- (Optional) Set a usage limit for this specific key – useful for sandboxing costs
- Click Create
Using Your API Key in Code
Here's how to use your key with the Claude API in Python:
import anthropic
client = anthropic.Anthropic(
api_key="sk-ant-..." # Replace with your actual key
)
message = client.messages.create(
model="claude-3-5-sonnet-20241022",
max_tokens=1024,
messages=[
{"role": "user", "content": "Hello, Claude!"}
]
)
print(message.content)
For TypeScript/Node.js:
import Anthropic from '@anthropic-ai/sdk';
const client = new Anthropic({
apiKey: 'sk-ant-...',
});
async function main() {
const message = await client.messages.create({
model: 'claude-3-5-sonnet-20241022',
max_tokens: 1024,
messages: [{ role: 'user', content: 'Hello, Claude!' }],
});
console.log(message.content);
}
main();
Best Practices for API Keys
- Never hardcode keys in source code. Use environment variables or a secrets manager.
- Rotate keys regularly – especially if you suspect a leak.
- Use separate keys for development, staging, and production environments.
- Set key-level usage limits to prevent runaway costs from a single application.
Step 3: Monitoring Usage and Setting Limits
One of the most important tasks in the Console is keeping an eye on your API usage. Unchecked usage can lead to unexpectedly high bills.
Viewing Usage
- Go to Usage in the sidebar
- You'll see a graph of token consumption (input + output) over time
- Below the graph, a table breaks down usage by API key, model, and date
- You can filter by date range, model, or specific key
Setting Spending Limits
To avoid surprises, set a billing limit:
- Go to Billing → Settings
- Under Spending Limit, toggle it on
- Enter your desired monthly limit (e.g., $100)
- Optionally set a soft limit – you'll receive an email alert when you reach, say, 80% of your limit
- Click Save
Usage Alerts
You can also set up email alerts for specific thresholds:
- In Billing → Alerts, click Create Alert
- Choose a metric (e.g., total cost, input tokens, output tokens)
- Set a threshold value and a time window (daily, weekly, monthly)
- Add recipients (email addresses)
Step 4: Managing Billing and Invoices
Your Company account's billing section is where you handle payments.
Adding a Payment Method
- Go to Billing → Payment Methods
- Click Add Payment Method
- Enter your credit card details (Anthropic uses Stripe for processing)
- Set it as your default payment method
Viewing Invoices
- Go to Billing → Invoices
- You'll see a list of all past invoices with amounts and payment status
- Click any invoice to download a PDF copy for your records
Understanding Pricing
Claude API pricing is based on tokens (input and output). As of this writing, pricing varies by model:
- Claude 3.5 Sonnet: $3 per million input tokens, $15 per million output tokens
- Claude 3 Haiku: $0.25 per million input tokens, $1.25 per million output tokens
- Claude 3 Opus: $15 per million input tokens, $75 per million output tokens
Step 5: Managing Team Members (Organization Accounts)
If you're building with a team, you can invite others to your Company account. This gives them access to the Console without sharing your API keys.
Inviting Team Members
- Go to Settings → Team
- Click Invite Member
- Enter their email address and select a role:
- Click Send Invite
Removing Members
To revoke access, go to Settings → Team, find the member, and click Remove. This immediately revokes their Console access, but any API keys they created will continue to work unless you also revoke those keys.
Troubleshooting Common Issues
"API key not found" errors
- Ensure you're using the correct key (check for typos)
- Verify the key hasn't been revoked
- Check that the key is associated with the correct Company
Rate limiting
If you receive 429 errors, you're hitting rate limits. Solutions:
- Implement exponential backoff in your code
- Request a rate limit increase via the Console (Billing → Request Limit Increase)
- Distribute requests across multiple keys (not recommended for most use cases)
Billing disputes
If you believe you've been overcharged, contact Anthropic support via the Console's help widget (bottom-right corner) or email [email protected].
Key Takeaways
- Your Company account is the central hub for managing Claude API access, keys, billing, and team members.
- Always use environment variables for API keys and rotate them regularly to maintain security.
- Set spending limits and alerts to prevent unexpected costs – this is critical for production deployments.
- Use separate API keys for different environments (dev, staging, production) to isolate issues and track usage per application.
- Invite team members with appropriate roles instead of sharing a single API key – this improves security and auditability.