MeanCEO: Tech Startups and Startup Ideas

Claude Linked Billing: Your Customers Can Now Pay Anthropic Directly for the AI in Your App. The Catch: No Token Markup, No Relays, and Their Data Settings Don't Apply

TL;DR: What is Claude linked billing?

On 17 November 2026 Anthropic launched linked billing in beta. Apps built on Claude can now bill the Claude API usage they run for a customer straight to that customer's own Claude Platform organization, and no API key changes hands. The customer approves the link, sets a monthly cap for your app and can unlink at any time. You decide on each request whether the customer or you pays. The catch: it only works for customers who pay Anthropic directly, you can't mark up the usage Anthropic bills them, and the requests run under your account's data settings, not theirs.
If you sell an AI product on top of Claude, your biggest risk isn't the model. It's the bill. One heavy user can burn through your margin in a weekend, and the usual fix, asking customers to paste their own API key into your app, turns you into a vault for other people's passwords.
Anthropic now offers a third way. Here's what it launched, who can use it, what the terms forbid, and what it means for a small AI SaaS selling to European customers.

What Anthropic launched

Anthropic announced linked billing on the Claude Platform on 17 November 2026. Third-party platforms, such as coding agents and workflow tools, can let their end customers pay for Claude API usage "without sharing an API key". The customer links their Claude Platform organization to the app once, and Anthropic bills that organization directly.
On the developer side, the Claude API release notes describe it in two lines: once a customer has linked, you set a billing_policy on each request to the Messages or Chat Completions endpoint to choose who pays. If you mark a request for the customer and Anthropic can't bill them, the API refuses it. Anthropic says it "never silently bills you instead".
Anthropic named 19 platforms that support it at launch, including Asana, ClickHouse, Gumloop, Kilo Code, Linear, Mintlify, Railway, Ramp, Tines and Warp. Linear's Tom Moor summed up the pitch: "Manually copying API keys is inherently insecure." Railway on that list is telling: its final report on the October breach said attackers spent about $740,000 on stolen AI keys after decrypting customers' environment variables. A month later, one AI vendor's leaked key reached Cursor, Notion and Uber. Keys you never hold are keys nobody can steal from you.

How it works for you and your customer

Linked billing builds on the user profiles Anthropic launched in October, which we covered in our piece on Claude API user profiles. You create one profile per customer organization in your own Claude account. The customer clicks a "Link your Claude organization" button in your app, signs in to Claude, picks an organization, sets a monthly spend limit for your app and approves. From then on:
  • You choose who pays, request by request. Bill the customer for the work they ask your product to do, and pay yourself for free-tier features, trials or anything you want to include in your price.
  • The customer controls the spend. A user with the Owner, Admin or Billing role approves the link and can set a monthly cap for your app in whole US dollars, or a default for every linked app, and can unlink you in the Console. Their admins get emails at 80% and 100% of the cap, according to Anthropic's help article for customers.
  • You see usage per customer. Request counts, tokens and models per linked customer show up in your Console, but you can't see the customer's cap or the rates they pay.
  • You still support them. Anthropic handles the approval page and the bill. Every other question about your app comes to you.
Not every customer can link. The linked billing docs and the help article set clear limits:
Your customer pays for Claude throughCan they link to your app?
A Claude Platform (Console) organization with prepaid creditsYes
A Claude Platform organization with invoiced billingYes
The AWS, Google Cloud or Azure marketplaceNo
Amazon Bedrock, Vertex AI or Microsoft FoundryNo
Only a Claude plan (Pro, Max, Ultra, Team or Enterprise)No
No Claude account yetYes, after creating a free Console organization and adding credits
Sources: Anthropic linked billing docs and Claude Help Center, checked 20 November 2026. Credits from Anthropic's partner, VC and startup programmes, and the monthly API credits that come with Max, Ultra and Team plans, can't pay for linked usage.
There are technical gaps too. Message Batches can't bill the customer yet, so cheap overnight batch jobs stay on your bill. A successful response doesn't say who paid, so you need your own log. And when a customer unlinks, Anthropic sends you no webhook and no email: your next request for them just fails with a 403.

The fine print: no markup, no relays

The business rules sit in the Linked Billing Terms, which you accept when you publish your app. Read them before you build pricing around this feature, because a few lines decide whether it fits your business at all:
You mayYou may not
Charge your own fees for your productMark up, or separately charge for, the Claude usage Anthropic bills the customer
Bill the customer for requests they direct you to makeBill one customer's link for anyone else's requests, including your own testing
Follow the customer's instructions on which models to usePick models or options to increase a customer's usage
Build a product that transforms what goes in and outRun a gateway, router or proxy that just relays Claude
Link your own direct customersLink customers who reach you through another reseller
Power your own appUse a link to power Claude Code, Claude.ai or Claude for Work
Source: Anthropic Linked Billing Terms, checked 20 November 2026. If Anthropic decides you billed usage to a customer that wasn't theirs, it can credit the customer and charge you at your own rates.
The no-markup rule is the big one for bootstrappers. Today many AI micro-SaaS products bundle tokens into a subscription and earn a margin on them. With linked billing, the tokens are passed through at whatever rate the customer has with Anthropic, and your margin has to come from your own subscription, seat or platform fee. That's not a bad thing: it forces you to price the value of your workflow, not the cost of someone else's model. Our guide to competitive pricing for a bootstrapped SaaS is a good place to rethink that.
It also changes the risk math. At Anthropic's list prices, Claude Sonnet 5.5 costs $2 per million input tokens and $10 per million output tokens, and Claude Fable 5.2 costs $8 and $40. A customer whose agents push 30 million input and 3 million output tokens a month would cost about $90 on Sonnet 5.5 or about $360 on Fable 5.2 (our estimate at list prices, before caching or discounts). On a flat plan of, say, €29 a month, that customer loses you money. Billed to their own organization, they cost you nothing, and they decide how big the agent bill gets. For a wider look at why AI bills spiral, see our news on AI token costs running two to five times over budget.

The European catch: whose data settings apply?

This is the part EU founders should read twice. Linked billing moves the bill, not the data. Anthropic's announcement says the requests run in the platform's organization, "so settings in the customer's organization, such as IP allowlists, encryption keys, and data retention, don't apply." The docs add that a customer's zero data retention, business associate agreement and customer-managed encryption keys don't cover these requests, and tell platforms not to link customers who need that coverage.
The terms make it explicit: inputs and outputs are processed under your agreement with Anthropic, including your data processing agreement and your retention settings, and you are responsible for telling customers how their data is handled. In GDPR terms, nothing changes about who is who. You are still your customer's processor, and Anthropic is still your sub-processor. Under GDPR Article 28(2) (Adopted law), a processor can't engage another processor without the controller's prior written authorisation, so Anthropic belongs on your sub-processor list either way.
The risk is a misunderstanding. A European customer who negotiated zero data retention with Anthropic may assume it follows them into your app because "it's billed to our Claude account". It doesn't. Say so on your linking screen and in your DPA. Two smaller GDPR points: Anthropic may share a linked customer's name, email and organization name with you, and the terms make you independently responsible for using that only to run the link and delete it when you no longer need it. And when you create user profiles, every field is optional. Send hashes instead of names and emails where you can, which fits the data-minimisation principle in GDPR Article 5(1)(c) (Adopted law). Our GDPR compliance checklist for early-stage startups covers the rest.

What this means for you

  1. If you sell to developers or companies already on the Claude Platform, add it. It removes the scariest thing in your database (customer API keys) and the scariest line in your costs (unlimited token use). Start with your heaviest users.
  2. Keep a plan B for everyone else. Customers on Bedrock, Vertex AI, cloud marketplaces or only a Claude plan can't link. If many of your customers fall in that group, your own billing stays for now.
  3. Reprice before you switch. If your plan includes tokens, decide what your fee pays for once the tokens are billed elsewhere: the workflow, the integrations, the support. You can't add a token markup on top.
  4. Build the refusals in from day one. Handle the 402 (cap reached or no credit) and 403 (not billable or unlinked) errors with a clear message and, if you want, a fallback billed to you.
  5. Update your DPA and your linking screen. Tell EU customers in plain words that their own Anthropic data settings don't apply inside your app, and which settings do.
  6. Treat it as beta. Anthropic says the feature "might not be suitable for production use" and can change or end it. Don't rip out your existing billing yet. For the rest of this month's AI tool news, see our AI news for November 2026, and for the newest Claude model and its price, our Claude Fable 5.2 news.
My take: this is one of the most useful things Anthropic has shipped for small AI businesses this year, and it's hidden in a billing doc. The bootstrapper's nightmare is the power user on a flat plan, and this hands that cost back to the customer, with a cap they set themselves. The price is that you can no longer hide a token margin inside your plan, which, honestly, was never a moat. If your product is just a nicer window onto Claude, the terms already say you can't use linked billing for it. If your product does real work, this is how you stop subsidising your best customers. Just don't let the word "Claude" on the bill fool your European customers into thinking their own data settings came along.
Are you getting customers from AI search yet?

More and more traffic is coming from Perplexity, ChatGPT, Grok and other AI tools.

👉 Rank on ChatGPT

FAQ: Claude linked billing

What is Claude linked billing?

A beta feature of the Claude Platform, launched on 17 November 2026. It lets an app bill the Claude API usage it runs for a customer directly to that customer's own Claude Platform organization, after the customer approves a link. No API key is shared, and the app chooses on each request whether the customer or the app pays.

Who can pay through linked billing?

Only organizations that pay Anthropic directly, with prepaid credits or invoiced billing. Organizations that use Claude through AWS, Google Cloud or Azure, including Bedrock, Vertex AI and Foundry, and accounts with only a Claude plan such as Pro, Max or Team, can't link. Startup-programme credits can't pay for linked usage either.

Can I add a margin on the tokens my customer pays for?

No. Anthropic's Linked Billing Terms let you charge your own fees for your product, but not mark up or separately charge for the usage Anthropic bills to the customer. Your margin has to come from your own pricing.

Does my customer's zero data retention apply to requests in my app?

No. The requests run in your organization, so your data retention, encryption keys and data processing agreement apply. Anthropic tells platforms not to link customers who need zero data retention, a BAA or customer-managed encryption keys for that usage.

What happens when a customer hits their spend cap?

Requests you bill to them are refused with a 402 error until the first day of the next month (00:00 UTC) or until they raise or remove the cap. You can still serve them by resending the request billed to yourself.

Is linked billing ready for production?

It's a beta. Anthropic's docs say endpoints, parameters and behaviour can change and that it might not be suitable for production use. Until your app is approved, only test users can link, with a monthly cap of $50 or less.

About the Author

Violetta Bonenkamp, also known as MeanCEO, is an experienced startup founder with an impressive educational background including an MBA and four other higher education degrees. She has over 20 years of work experience across multiple countries, including 5 years as a solopreneur and serial entrepreneur. Throughout her startup experience she has applied for multiple startup grants at the EU level, in the Netherlands and Malta, and her startups received quite a few of those. She’s been living, studying and working in many countries around the globe and her extensive multicultural experience has influenced her immensely.
2026-11-20 04:15 News and Trends