On November 17, Anthropic launched a beta feature called Linked billing in the release notes for the Claude Developer Platform. Developers building applications on Claude can now charge the cost of API calls to the customer's own Claude organization account, rather than paying up front themselves and folding the cost into a subscription price charged to the customer.
For developers who sell enterprise software, what changes is whose desk the invoice lands on.

How it works
The process has two steps. The customer first links their Claude organization to the developer's application and completes authorization. After that, the developer chooses on each request whether the customer or the developer pays for it. Within a single application, some requests can be billed to the customer's account while others remain the developer's responsibility.
The request itself still runs on the developer's account, using the developer's usage limits and model access. The money comes from the customer's side, but which models can be called and how many requests can be made per minute remain whatever the developer has configured.
The customer has two controls on their side: set a monthly spending cap for each linked app in the Claude Console, or unlink the app at any time. If Anthropic cannot charge the customer, for example because the balance has run out or a payment has failed, the request is rejected outright and is not passed on to the developer to pay.
Who can't use it
The restrictions are spelled out in detail:
- It applies only to organizations that pay Anthropic directly. Enterprises that settle Claude usage through AWS, Google Cloud or Azure are not covered.
- Users who have only a Claude subscription and no API account cannot use it.
- Credits bundled with Claude plans and credits issued through Anthropic's startup support program cannot be applied to these charges.
- Data protection agreements that the customer has signed with Anthropic, such as zero data retention or HIPAA, do not cover requests sent through the developer's application.
That last point matters most for regulated industries. Even if a healthcare provider has a HIPAA agreement with Anthropic, it cannot assume that protection still applies when it calls Claude through a third-party app using linked billing.
Public reports so far do not say which regions the beta is open in, when it will move to general availability, or whether there is any grace period once a spending cap is hit. Anthropic has also not published separate rates for the feature.
How it compares with OpenAI's approach
The two companies have taken different routes to getting end users to pay for themselves.
OpenAI lets ChatGPT users sign in to third-party tools such as OpenClaw with their subscription account, drawing on the allowance in a consumer plan. Anthropic, for its part, excluded subscribers from using OpenClaw in April this year, and linked billing likewise shuts subscribers out: the only thing it recognizes is an API organization account.
On OpenAI's path, the payer is an individual's subscription account, and the plan tier caps how much can be spent. On Anthropic's path, the payer is a company's API organization, and the customer sets the cap app by app. The former is aimed at individual users, while the latter is clearly aimed at enterprise procurement.
Anthropic had already let companies use API budgets to buy Claude-based applications through its own app marketplace. Linked billing takes that a step further: an application no longer needs to be listed in the marketplace to draw directly on a customer's API budget.
For developers, the upside is that they no longer have to prepay inference costs for large customers or design separate pricing tiers for customers whose usage swings widely. The cost is having to convince the customer's IT and legal teams to accept that their Claude account will be called by a third-party application, particularly when their data protection agreements do not cover those calls.
Sources: Anthropic Claude Developer Platform release notes, The Next Web, CocoLoop; the scope of eligibility, the data protection exception and how failed charges are handled are as described by Anthropic.