Anthropic Launches Claude API Linked Billing Beta
On November 17, 2026, Anthropic launched the Linked billing Beta, allowing developers to bill Claude API usage to their customers' own Claude organizations, with the option to choose per request whether the customer or the developer pays. Requests still execute within the developer's organization, so the developer's rate limits, model access, and service tiers apply as usual; if the customer cannot be billed, the API rejects the request rather than silently shifting the cost to the developer. This feature is only supported for Claude Platform organizations that pay directly via prepaid credits or invoicing, and Message Batches and billable code execution features do not support customer billing.
Body
Anthropic launched Linked billing in beta on November 17, 2026, allowing developers to bill Claude API usage in their applications to a customer’s own Claude organization. Once a customer has linked its organization, the developer can choose on each request whether the customer or the developer pays.
Anthropic’s user-profile documentation distinguishes identification from payment. A profile tells Anthropic which end customer a request serves, so a safety restriction or ban can be limited to that customer rather than the developer’s entire organization. Profiles alone do not alter billing or pricing; Linked billing adds payer selection to that attribution system.
Per-Request Billing
In the default integration, the app sends the customer’s profile ID in the anthropic-user-profile-id header. On /v1/messages and /v1/chat/completions, setting billing_policy with bill_to: "user_profile" designates the linked customer as the payer. Setting bill_to: "self" or omitting the policy leaves the developer responsible. Calls that include billing_policy must also carry the user-profiles-billing-2026-10-01 beta header.
The payer selection does not move execution into the customer’s account. Requests still run in the developer’s organization, so the developer’s rate limits, model access, and service tier apply. If Anthropic cannot bill the customer for a request marked user_profile, the API refuses it instead of silently charging the developer. The developer can still serve that customer at its own cost by resending with bill_to: "self".
Coverage has technical exclusions. Message Batches does not support customer billing, and a customer-billed Messages request cannot use billable code-execution features. The token-counting endpoint accepts billing_policy but ignores it, so developers can count tokens on the same request body they intend to send.
Customer Authorization and Controls
An app adds a Link your Claude organization button to start the connection. The user signs in to Claude, selects an organization when offered a choice, reviews the billing explanation, and can set a monthly spend limit for a live app before giving final authorization. The approver needs the Admin or Billing role in the customer organization. Developers must also register an OAuth app, configure client authentication through an identity provider rather than a client secret, and designate an operator service account.
Connections are one-to-one within an app: a customer organization can link to only one user profile, and a profile can link to only one Claude organization. The operator service account can bill any linked customer by default. For single-tenant deployments or customer-controlled sandboxes, optional connection-bound OAuth access tokens can bill only their associated customer and expire within one hour.
Customers manage their connections on the Claude Console’s Linked platforms page. An app-specific monthly cap is separate from the organization’s overall monthly spend limit, and reaching either one causes customer-billed requests to be refused. The cap counts token costs and web search fees at list prices before any negotiated discount, so the counted amount can differ from the customer’s bill. Customers can also unlink an app at any time. Subsequent customer-billed requests are refused, and Anthropic sends the developer no notification when a customer unlinks.
Eligibility and Data Limits
Only Claude Platform organizations that pay Anthropic directly through prepaid credits or invoiced billing are eligible. Organizations billed through AWS, Google Cloud, or Azure marketplaces cannot be billed through the integration, and neither can organizations with only a Claude subscription plan. Monthly API credits included with Claude Max, Ultra, and Team plans cannot pay for these requests, nor can credits from Anthropic’s partner, venture capital, and startup programs. A completed connection therefore does not guarantee that Anthropic can bill the customer.
Data handling remains under the developer’s arrangements as well. The customer’s zero-data-retention setting, business associate agreement, and customer-managed encryption keys do not apply to these requests. Anthropic instructs developers not to link customers whose usage requires HIPAA or FERPA privacy coverage or those encryption controls.
Linked billing consequently changes who pays without changing where the request runs. It gives Claude-based applications a built-in customer-payment option, while customer eligibility, endpoint support, and the developer’s own retention and compliance terms determine where that option can be used.
AI Trends