Claude linked billing beta connects outside tools to your API bill
Edited and reviewed by AI Ping Editorial Team
3-line summary
- Anthropic launched the beta on November 17 with 19 supporting platforms.
- It serves directly billed API organizations, separately from Pro and Max subscriptions.
- Customers control app spending caps; the provider’s processing settings apply.
Anthropic launched linked billing on the Claude Platform in beta on November 17. Customers can approve an organization link instead of giving a third-party tool their API key, with Claude API usage billed directly to their own organization. The launch lists 19 platforms, including Factory, Linear and Ramp. Customers can draw on an existing Anthropic commitment or pay as they go.
Eligibility covers organizations that pay Anthropic directly for API usage. Monthly Claude subscriptions such as Pro and Max are separate, as are API accounts billed through cloud providers or cloud marketplaces. The connection transfers billing; requests still run under the tool provider's organization settings.
An administrator or billing user approves the organization-wide link on Anthropic's approval page. Providers choose the payer on each request. If a customer-designated request cannot be charged, the API rejects it without automatically shifting the bill to the provider. Providers handle support for their apps; Anthropic supplies the approval and Console billing controls. The approval page identifies the app and what it is requesting. Providers may charge customers only for work those customers direct them to perform, excluding the provider's own usage.
Purchased prepaid API credits or an invoicing arrangement can fund usage. The monthly API credits included with Max, Ultra and Team plans cannot pay for third-party usage through linked billing. Purchased credits expire one year after purchase and are non-refundable.
App limits use list prices
Customers can set monthly limits for individual linked apps in Console. A default applies separately to each app, alongside the organization's overall monthly spending limit. Reaching either limit blocks new customer-paid requests.
The cap counts token and web-search charges at list prices before negotiated discounts, so the amount counted toward a limit can differ from the eventual bill. The allowance resets at midnight UTC on the first of the next month unless the cap is raised or removed earlier.
The analytics API breaks down requests and tokens over time by dimensions including model. Cost responses distinguish the platform's own cost from list prices. Its cost is zero for customer-paid requests; it cannot see the customer's actual bill. Data typically lags by four hours and can take up to 24 hours. Responses include a refresh timestamp, and monthly figures can be revised until about the seventh day of the following month. Usage reports distinguish cached input, fresh input and output tokens; time buckets can be minutes, hours or days in UTC.
Processing follows the platform's organization: its rate limits, model access and service tier apply. The customer's IP allowlist, encryption keys and retention settings do not carry over to those requests.
Customer-paid billing in this beta covers the Messages and Chat Completions APIs. Message Batches and Claude Managed Agents are excluded. The OAuth overview warns that beta features and behavior may change.
Launch partner Harness said Claude usage in its Cosmos Software Factory Agent can be billed on a customer's existing organization terms. Cosmos subscriptions are charged separately, and API-key connections remain supported. Harness says the agent draws on code, tickets and build, deployment and security information, with customers determining permitted changes, required checks and human approval points. Its workflows connect to existing Harness policies, permissions and approvals. Harness describes an agent that takes work items toward reviewable code changes and brings people in at checkpoints.
Customers can unlink an app in Claude Console. New customer-paid calls typically stop within about ten seconds, the documentation says. Requests already running continue to completion and are billed to the customer.
Sources
- Linked billing on the Claude Platform — November 17, 2026 — Anthropic
- Claude Platform OAuth: approval, request payer and provider support — Claude Platform Docs
- Offer linked billing in your platform: eligibility and processing scope — Claude Help Center
- Linked billing: spend caps and unlink behavior — Claude Platform Docs
- Usage and Cost Analytics API: amounts and data freshness — Claude Platform Docs
- Cosmos by Harness Now Supports Linked Billing with Claude Platform — Harness
- How do I pay for my Claude API usage? — purchased and subscription credits — Claude Help Center
