Skip to main content

Authentication

Normal API requests use a Standard Compute API key. Create and manage keys in the dashboard.

Company-managed Claude Microsoft sign-in uses each employee’s Microsoft access token on the company-specific eu.stdcmpt.com/entra/… connection instead. Standard Compute resolves that identity to the employee’s individual company key for access and usage; employees do not copy the key into Claude. This token flow is not available on the normal API-key endpoints.

Sending your key​

Send the key as a bearer token:

Authorization: Bearer YOUR_API_KEY

The Messages API also accepts the Anthropic-style header, so Anthropic SDKs work unchanged:

x-api-key: YOUR_API_KEY

If both headers are present, Authorization is used.

Keeping keys safe​

  • Store keys in environment variables or your tool's secret store, not in source code.
  • Never send a key in a URL query parameter.
  • If a key leaks, rotate it in the dashboard to revoke the old one.

Company keys​

In a company workspace, admins create keys for members, teams and the company. Each key carries its own plan, approved by an admin, or draws from the company's Pay as you go balance (usage plus 7.5% on Teams, 10% on Enterprise); a member's extra keys can share that member's plan. When a key's budget is used, only that key stops with 402. With the launcher, add --choose-key to pick between your personal and company keys.

Errors​

A missing or invalid key returns 401. A company key that has been disabled returns 403. See Errors.