Anthropic Lets Claude Apps Bill AI Costs to Customers' Accounts
Anthropic has launched Linked billing in beta, which lets a Claude app charge the cost of requests to the customer's own account instead of the developer's. The customer links their organization once, and in each request the developer chooses who pays. If the charge to the customer fails, the request is rejected, and no bill goes to the developer. This makes it easier for small AI products to avoid taking on unpredictable token costs.
AI-processed from TNW; edited by Hamidun News
If you build a product on top of Claude, you probably have the same headache: users pay a fixed subscription, while tokens cost a variable amount. A single active customer can spend more in a week than the product brings in over a year. Anthropic has released Linked billing in beta, which removes part of this problem: model costs can be shifted to the customer's own account.
How Linked billing works
The setup is simple. The customer links their organization in Claude to your app and confirms access. After that, the developer specifies in each request who pays: the developer or the customer. This is convenient for mixed pricing. For example, short hints in the interface remain on your bill, while heavy analysis of hundreds of documents is charged to the customer.
An important detail: the request itself still runs on the developer's account. Usage limits and model access are taken from there. Only the account that the money is drawn from changes.
The customer gets control over spending. In the Claude Console, they can set a monthly limit for each app separately or unlink it at any time. If Anthropic cannot charge the customer, the request is rejected. It does not turn into a bill for the developer. For you, this is protection from the unpleasant scenario where the customer runs out of funds and the costs land on your card.
Who this won't suit
The beta has many limitations. The feature works only for organizations that pay Anthropic directly. If a customer buys Claude through AWS, Google Cloud or Azure, they cannot be linked. Customers who have only a Claude subscription are also excluded. Credits from Anthropic's pricing plans and startup programs cannot be spent this way either.
For enterprise buyers, this matters a lot. Large companies often purchase models through a cloud provider to cover costs under a single corporate contract. They are left out until Linked billing is expanded.
The privacy catch
There is a second caveat that is easy to miss. The customer's own data protections do not extend to these requests. If an organization has zero data retention configured or has signed a HIPAA agreement, that does not carry over to requests that go through the developer's app. The request is processed under the terms of the developer's account.
For medical, legal and financial products, this can be decisive. The customer may think they are paying from their protected account and that the terms move along with the payment. In reality, they do not. Developers should state this explicitly in the linking interface and in the contract, or the misunderstanding will quickly become a compliance problem.
What this means for the market
Anthropic is consistently deciding who pays for heavy usage. In April, the company restricted subscribers from routing third-party tools through their subscription, while OpenAI, by contrast, lets ChatGPT users connect apps using their own subscription. Linked billing fits the same pattern: AI costs are increasingly assigned to whoever receives the benefit, not to whoever built the interface.
The practical takeaways for teams are as follows.
- If your customers are companies that pay Anthropic directly, Linked billing lets you move to a "bring your own key" model without doing your own token cost calculations.
- If customers buy through clouds, you will have to keep the existing scheme with a subscription markup for now.
- If you work with sensitive data, first check which customer guarantees do not transfer, and clearly state this in your terms.
The feature is in beta, and details may change. But the principle itself is useful: for AI startups, this is a chance to tie their costs to actual usage rather than guessing at them when setting prices.
- Nov 22, 2026Claude Code removed ads from a TV in 90 minutes and kicked off a gadget-hacking trend
- Nov 22, 2026Agent Ignored AGENTS.md: In a Third of Pushes It Didn't Ask, and Force-Pushed 31 Times
- Nov 22, 2026Axiom Math's AI Writes 43.1 Million Lines of Lean Proof in 24 Days
- Nov 22, 2026Yandex Grant Funds an LLM Engine: 35B Model on RTX 2080 Ti Runs Three Times Faster Than llama.cpp
Key Questions Answered
How Linked billing works?
The setup is simple. The customer links their organization in Claude to your app and confirms access. After that, the developer specifies in each request who pays: the developer or the customer. This is convenient for mixed pricing. For example, short hints in the interface remain on your bill, while heavy analysis of hundreds of documents is charged to the customer. An important detail: the request itself still runs on the developer's account. Usage limits and model access are taken from there.
Who this won't suit?
The beta has many limitations. The feature works only for organizations that pay Anthropic directly. If a customer buys Claude through AWS, Google Cloud or Azure, they cannot be linked. Customers who have only a Claude subscription are also excluded. Credits from Anthropic's pricing plans and startup programs cannot be spent this way either. For enterprise buyers, this matters a lot. Large companies often purchase models through a cloud provider to cover costs under a single corporate contract.
What are the key details on The privacy catch?
There is a second caveat that is easy to miss. The customer's own data protections do not extend to these requests. If an organization has zero data retention configured or has signed a HIPAA agreement, that does not carry over to requests that go through the developer's app. The request is processed under the terms of the developer's account. For medical, legal and financial products, this can be decisive.
Test Frontier LLMs & Autonomous Agents in One Workspace
Run Claude Opus 5.5, GPT-6, Gemini 3.1, and DeepSeek side-by-side in Nomad AI (nomadnet.ai) — unified model routing, deep research, and multimodal workflows under one subscription.
The AI world, distilled — once a week
Seven stories that actually mattered, hand-picked. No noise, no reposts, no press releases.
Done! Check your inbox for a confirmation.