Anthropic Opens Linked Billing Beta for Claude API Apps
Anthropic’s Nov. 17 beta lets Claude API apps charge a customer’s organization per request while execution stays with the developer, with strict caps and exclusions.
By Grace Kim
4 min read

What's News
- Anthropic launched Linked billing in beta on November 17, 2026.
- The `user-profiles-billing-2026-10-01` beta header must accompany requests that set `billing_policy`.
- Two monthly spending limits—an app-specific cap and an organization-wide limit—can each block customer-billed requests.
- Optional connection-bound OAuth access tokens expire within one hour.
- Only Claude Platform organizations paying Anthropic directly through prepaid credits or invoiced billing qualify.
By Grace Kim
Anthropic launched a Linked billing 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 links that organization, the developer can choose on each request whether the customer or the developer pays.
What changes for Claude API developers?
Anthropic’s user-profile documentation separates identification from payment. A profile tells Anthropic which end customer a request serves, so Anthropic can limit a safety restriction or ban to that customer rather than the developer’s entire organization. Profiles alone do not change billing or pricing; Linked billing adds payer selection to that attribution system.
Developers send the customer’s profile ID in the anthropic-user-profile-id header. Anthropic’s documentation says /v1/messages and /v1/chat/completions requests use billing_policy. With bill_to: "user_profile", the linked customer pays. bill_to: "self" or an omitted policy leaves the developer responsible. Those calls must also include the user-profiles-billing-2026-10-01 beta header.
Execution remains inside the developer’s Anthropic organization. Anthropic therefore applies the developer’s rate limits, model access and service tier even when the linked customer pays for the request.
If Anthropic cannot bill a request marked user_profile, Anthropic refuses the call instead of silently charging the developer. The developer can resend it with bill_to: "self" and serve the customer at the developer’s own cost. Linked billing changes the payer, not the place where the request runs.
How do customers authorize and control spending?
Anthropic’s “Link your Claude organization” flow starts when an app adds that button. The user signs in to Claude, selects an organization when offered a choice, reviews the billing explanation, and can set a monthly spending limit for a live app before giving final authorization. The approver must hold the Admin or Billing role in the customer organization.
Anthropic requires developers to register an OAuth app, configure client authentication through an identity provider rather than a client secret, and designate an operator service account.
Anthropic limits connections to one-to-one links 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, Anthropic offers optional connection-bound OAuth access tokens. Those tokens can bill only their associated customer and expire within one hour.
Customers manage links on the Claude Console’s Linked platforms page. Anthropic keeps an app-specific monthly cap separate from the organization’s overall monthly spend limit. Reaching either cap makes Anthropic refuse customer-billed requests. The app cap counts token costs and web search fees at list prices before negotiated discounts, so the counted amount can differ from the customer’s actual bill.
Customers can unlink an app at any time. Anthropic refuses subsequent customer-billed requests and does not notify the developer when a customer disconnects. Customers retain three levers after approval: a monthly cap, a separate organization limit and the ability to disconnect.
Which endpoints and customers qualify?
Linked billing does not cover every Claude API route. Anthropic says 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, allowing developers to count tokens on the same request body they plan to send.
Anthropic limits eligibility by how the Claude organization pays. Only Claude Platform organizations that pay Anthropic directly through prepaid credits or invoiced billing qualify. Anthropic excludes organizations billed through AWS, Google Cloud or Azure marketplaces, as well as organizations that have only a Claude subscription plan.
Monthly API credits included with Claude Max, Ultra and Team plans cannot pay for customer-billed requests. Anthropic also excludes credits from its partner, venture capital and startup programs. A completed connection therefore does not guarantee that Anthropic can bill the customer. A direct, collectible billing relationship with Anthropic remains the gating requirement.
What happens to data and compliance controls?
Data handling remains under the developer’s arrangements. Anthropic says 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.
Anthropic said: “Linked billing changes who pays without changing where the request runs.” The beta gives Claude-based applications a built-in customer-payment option, while eligibility, endpoint support and developers’ retention and compliance terms determine where they can use it. For now, the feature offers a flexible payer switch, not a new execution or compliance architecture.
Source: unite.ai
More from Grace Kim
Show full bio
Market editor covering people, launches and day-to-day practice in entrepreneurship, startups and venture funding at Business Bearings.
2,301 articles