Anthropic launches linked billing for customer-paid Claude API use
Anthropic’s November 17, 2026 beta lets developers bill selected Claude API calls to a customer’s Claude organization, with eligibility, spend-cap, endpoint, and data-control limits.

Why it matters
- Anthropic launched linked billing in beta on November 17, 2026.
- `bill_to: "user_profile"` on supported endpoints requires the `user-profiles-billing-2026-10-01` beta header and makes the linked customer the payer.
- Each app allows a one-to-one link between a customer organization and user profile.
- Optional connection-bound OAuth tokens expire within one hour.
- Customers can unlink at any time, and Anthropic sends the developer no notification.
By Sophie Lindqvist
Anthropic launched linked billing in beta on November 17, 2026, letting developers charge selected Claude API requests to a customer’s linked Claude organization. Once a customer connects that organization, the developer can choose on each request whether the customer or the developer pays.
Anthropic says the feature gives multi-tenant applications a built-in customer-payment option without shifting request execution into the customer’s account. The separation lets an app vendor recover metered API costs from customers while keeping model access, rate limits, and service tier under the developer’s organization.
What does linked billing change?
Anthropic says linked billing changes who pays, not where a request runs. Every request stays in the developer’s organization, so the developer’s rate limits, model access, and service tier still apply.
The feature builds on Anthropic’s user-profile system. A profile identifies the end customer for a request, so a safety restriction or ban can be limited to that customer rather than the developer’s entire organization. The enforcement target can therefore be narrower than the app’s whole customer base.
Profiles alone do not alter billing or pricing; linked billing adds payer selection to that attribution system. In plain terms, the profile identifies the customer, while the billing policy determines the wallet.
How does a customer authorize an app?
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, and reviews the billing explanation. For a live app, the user can set a monthly spend limit before final authorization.
Developers must also register an OAuth app. They must configure client authentication through an identity provider rather than a client secret, and designate an operator service account.
The customer remains the approval point. Anthropic requires the final approver to hold the Admin or Billing role inside the customer organization, while the developer supplies the OAuth and service-account machinery needed to make later requests.
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. Anthropic says the operator service account can bill any linked customer by default. The one-to-one rule prevents a single profile from serving as a billing bridge to several organizations within one app.
For single-tenant deployments or customer-controlled sandboxes, optional connection-bound OAuth access tokens can bill only their associated customer. Those tokens expire within one hour. The shorter-lived tokens give narrower deployments a tighter credential boundary.
How does the developer select the payer?
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, a request can set billing_policy with bill_to: "user_profile" to make the linked customer the payer.
Setting bill_to: "self" or omitting the policy leaves the developer responsible. Any call that includes billing_policy must also carry the user-profiles-billing-2026-10-01 beta header.
The profile header identifies whose request it is; the billing policy decides who pays for it. Anthropic keeps those signals separate because identification alone does not alter billing or pricing.
What happens when Anthropic cannot bill the customer?
If Anthropic cannot bill a customer for a request marked user_profile, the API refuses that request. Anthropic says it will not silently charge the developer instead, preventing an unexpected transfer of cost.
The developer can still serve that customer at its own cost by resending the request with bill_to: "self". The default is refusal, not a surprise developer charge. This fallback keeps service available while making the cost choice explicit.
Which API requests support customer billing?
Coverage has several technical limits. Anthropic lists these exclusions:
- Message Batches does not support customer billing.
- A customer-billed Messages request cannot use billable code-execution features.
- The token-counting endpoint accepts
billing_policybut ignores it, so developers can count tokens using the same request body they intend to send.
These exclusions mean linked billing does not cover every API feature. Developers must keep customer-paid traffic on supported paths.
What spending controls can customers use?
Customers manage their connections on the Claude Console’s Linked platforms page. An app-specific monthly cap is separate from the customer organization’s overall monthly spend limit, and reaching either limit causes customer-billed requests to be refused.
Anthropic says the app cap counts token costs and web search fees at list prices before any negotiated discount. As a result, the counted amount can differ from the customer’s actual bill. A displayed cap total is not necessarily a final invoice total.
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.
Which organizations can pay through linked billing?
Only Claude Platform organizations that pay Anthropic directly through prepaid credits or invoiced billing are eligible. The restriction applies before a customer can fund requests:
- Organizations billed through AWS, Google Cloud, or Azure marketplaces cannot be charged through linked billing.
- Organizations with only a Claude subscription plan are also ineligible.
- Monthly API credits included with Claude Max, Ultra, and Team plans cannot pay for customer-billed requests.
- Credits from Anthropic’s partner, venture capital, and startup programs cannot pay either.
A completed connection therefore does not guarantee that Anthropic can bill the customer. Eligibility depends on the organization’s existing payment arrangement, not just the OAuth link. Connection status and billing status remain separate checks.
What happens to data and compliance controls?
Anthropic says data handling for these requests remains under the developer’s arrangements. The customer’s zero-data-retention setting, business associate agreement, and customer-managed encryption keys do not apply to linked-billing requests.
Anthropic instructs developers “not to link customers whose usage requires HIPAA or FERPA privacy coverage or those encryption controls.” Direct customer payment therefore does not transfer the customer’s full compliance posture to the developer’s API request.
A linked customer can become the payer without importing the customer’s organization-wide privacy controls. Payer identity and data protection remain separate in the beta.
What should developers test before launch?
Developers should test the customer-payment path on /v1/messages and /v1/chat/completions, including both required headers and the refusal behavior when a customer cannot be charged. They should also verify spend-cap handling, unlinking, endpoint exclusions, and the data terms that apply to their own organization.
For multi-tenant Claude applications, linked billing offers a direct route to customer reimbursement while execution remains with the developer. The practical next step is to treat payer choice, spend controls, endpoint coverage, and compliance as separate launch checks.
Source: unite.ai
More from Sophie Lindqvist
Show full bio
Staff writer covering regulation, policy and their impact on artificial intelligence and machine learning at AI In Context.
749 articles
Related articles
- Anthropic expands Claude Startups program with up to $45,000 in credits
- Anthropic gives startups a free year of Claude Team and $1,000 in API credits
- Anthropic launches Personal Finance in Claude with read-only bank access
- Anthropic places 5% of shares in public benefit fund tied to AI displacement
- Zendesk kills per-seat pricing with Outcome AI Platform launch