Claude API linked billing (beta): let customers pay for their own usage
In brief
Linked billing lets your app's customers link their own Claude organization and pay for the Claude usage they cause, with a spend cap they set. You choose who pays on each request. It's in beta, works only for orgs that pay Anthropic directly, and doesn't cover batches or code execution.
Contents
Short answer: with linked billing (beta, since November 17, 2026), a customer of your app clicks "Link your Claude organization", sets a monthly spend cap, and from then on you can bill their Claude usage to their org instead of yours. You pick who pays on each request with billing_policy. No shared API keys. It only works for customers whose org pays Anthropic directly (credits or invoice).
Source: Anthropic's linked billing docs and release notes.
Who is it for?
- SaaS and dev tools whose users are mostly Claude Platform customers already.
- Apps where heavy users drive most of the cost and you'd rather they pay Anthropic directly than you mark it up.
- Teams that used to ask customers to "paste your API key here". Linking replaces that.
How it works
- Create an OAuth app in the Claude Console with the "Bill and link to organizations" option (needs the Admin role).
- The customer links once. You send them to Claude's sign-in page. An Admin or Billing person at their org picks the org, reads how billing works, sets a monthly cap, and approves. You get back a connection for that customer.
- On each request, send the customer's user profile header and set
billing_policyto choose who pays: you or the customer. Requests that set it need the beta headeruser-profiles-billing-2026-10-01. - The customer stays in control. In the Console they can change the cap or unlink your app at any time.
Safe by design: if a request marked "customer pays" can't be billed to them (unlinked, over the cap, no balance), the API refuses it. It never quietly bills you instead.
The rules that trip people up
- Eligible orgs only. Orgs billed through AWS, Google Cloud or Azure marketplaces, and subscription-only orgs, can't link (
403 user_profile_not_billable). - Plan credits don't count. The monthly API credits that come with Max, Ultra or Team plans, and startup or partner credits, can't pay for linked requests. Console-bought credits and invoices can.
- Spend cap hit: requests get
402until the 1st of the month (UTC) or until the customer raises the cap. - Your org's settings apply. Requests still run in your organization, so your rate limits and data retention apply. The customer's zero data retention, BAA or own encryption keys don't carry over.
- Not supported: Message Batches and billable code execution can't be billed to the customer.
- Testing first. A new app works only for test users, with a cap of $50 or less, until it's published. Publishing needs a domain check and review (invoiced orgs skip the wait).
Should I use it?
- Yes if your customers already have Claude Platform orgs and usage costs vary a lot per customer.
- Not yet if most customers are on cloud marketplaces, rely on plan credits, or need their own ZDR or BAA to apply.
Related: cutting Claude API costs, message threads, and securing your Claude app.
Quick answers
What is Claude API linked billing? A beta feature that lets your app's customers link their own Claude organization so their usage is billed to them, with a monthly spend cap they control.
Do customers have to share their API key with my app? No. They link their organization through Claude's sign-in page, and your app sends a user profile header on each request.
Can Max, Ultra or Team plan credits pay for linked billing? No. Only Console-bought credits or invoiced billing count. Plan credits and startup or partner credits don't.
What happens when a customer hits their spend cap? Requests billed to them fail with a 402 error until the 1st of the next month (UTC) or until they raise the cap. You are never billed in their place.