> For the complete documentation index, see [llms.txt](https://docs.warp.dev/llms.txt).
> Markdown versions of each page are available by appending .md to any URL.

# Managing Claude linked billing

Link your Claude organization to Warp through OAuth, enable linked billing for teams, and manage Anthropic spending separately from Warp usage.

Link your Claude organization to Warp through OAuth to pay Anthropic directly for eligible Claude usage at your organization’s API rates. No API key is needed.

Claude linked billing is available only on Warp Enterprise, with an active agreement and access to the feature. Contact your Warp account team if the linking controls aren’t available.

Public preview limitations

If your workload requires HIPAA or FERPA compliance, or customer-managed encryption keys (CMEK), do not use Claude linked billing during public preview.

## How linked billing works

Your workspace shares one link to a Claude organization. Each team opts in separately to charge its Claude usage to that organization instead of its Warp balance. Teams that don’t opt in keep their existing billing method.

Only the billing relationship moves to your Claude organization. Requests still run in Warp’s organization, so Warp’s organization settings govern retention, including applicable Zero Data Retention (ZDR), rate limits, and enabled features. Your Claude organization’s ZDR settings, IP allowlists, and encryption keys do not carry over.

## Supported Claude usage

Linked billing covers the Warp Agent on desktop, CLI, web, and cloud, including subagents and factory runs billed to the team. It doesn’t apply to Claude Code or other tools that connect directly to Anthropic.

Linked billing uses Anthropic’s API directly, not Amazon Bedrock, Vertex AI, or custom endpoints. It doesn’t expand the models available to your team.

## Before you link

-   Permission to manage billing for your Warp workspace. Workspace owners and admins have this permission.
-   A Claude organization with Anthropic API billing and linked billing access. You need an Owner, Admin, or Billing role to approve the link.

Claude Pro, Max, Team, and Enterprise subscriptions and their included usage don’t fund linked billing.

## Linking your workspace

1.  In Warp’s Enterprise [Admin Panel](https://docs.warp.dev/enterprise/team-management/admin-panel/), open your workspace settings and click **AI**.
2.  In the “Claude Linked Billing” section, click **Link your Claude organization**.
3.  In Claude’s approval flow, select the organization that will pay for Claude usage, review the billing authorization, and approve the link.
4.  After returning to Warp, check for “Claude organization linked.”

## Enabling a team

A team or workspace admin can enable linked billing after the workspace is linked:

1.  In the Enterprise Admin Panel, select the team and click **Models**. Remove any custom Claude endpoint configuration.
2.  In the “Anthropic” settings, select **Linked billing**, then click **Save**. If the panel instead shows **Use linked billing**, click that button.
3.  If the team has a saved Anthropic API key, review the removal warning and click **Remove key and save** to switch. You’ll need to enter the key again to switch back.

Linked billing is now enabled for the team, including [fallback to Warp billing](#if-linked-funds-run-out). Members can’t override this choice with personal Anthropic keys.

## Managing spending

Use [Claude Console’s Linked Platforms page](https://platform.claude.com/linked-platforms) to manage the link’s spending limit.

### If linked funds run out

If Anthropic declines a request for lack of linked funds, Warp can charge that request to your team’s Warp balance. Normal Warp spend limits apply; if Warp funding isn’t available, the request stops.

Problems with the link, rate limits, and other errors don’t switch billing. Warp doesn’t restart a response that has already begun.

### Other Warp charges

Anthropic and Warp don’t both bill the same inference. Warp bills fallback inference. Other-provider usage, tools, platform usage, and Warp-hosted compute can also incur charges under your [Enterprise billing terms](https://docs.warp.dev/enterprise/support-and-resources/billing/).

A spending limit in Claude Console doesn’t limit these separate Warp charges. Usage already incurred remains billable.

## Relinking or stopping linked billing

To renew the link, return to the workspace’s **AI** settings and click **Reconnect**.

To stop linked billing for one team, open its **Models** settings, select **Default**, and click **Save**, or click **Stop using linked billing** if shown.

To stop linked billing for every team in the workspace:

1.  In the workspace’s **AI** settings, click **Disconnect from Warp** and confirm.
2.  Check each team’s **Models** settings to confirm linked billing is off.

New requests use Warp billing or permitted API keys. Requests already in progress keep their original billing method.

Unlinking in Warp doesn’t revoke the authorization in Claude Console. To revoke it or link a different organization, open **Linked Platforms** in Claude Console and unlink Warp.

After relinking, enable each team that should resume linked billing.

## Related pages

-   [Bring Your Own API Key](https://docs.warp.dev/agents/inference/bring-your-own-api-key/) - Connect a provider account with an API key instead
-   [Team-managed API keys and endpoints](https://docs.warp.dev/enterprise/enterprise-features/team-managed-keys-and-endpoints/) - Manage alternative team inference configurations
-   [Plans and billing](https://docs.warp.dev/support-and-community/plans-and-billing/)
