Anthropic linked billing beta lets customers pay for Claude usage in your app (Python 2.10.0, TypeScript 1.10.0, November 17, 2026)
Send billing_policy with a user profile header to bill a linked customer's Claude org. Handle new 402/403 refusals; batches can't use it.
Your keys
0 of 1 ready
Create each key on its own page, paste it below, then copy the finished lines into your project's .env file. Your keys stay in this tab. They are never sent to Wirestack or saved; we only count that the panel was used.
- Anthropic API keyANTHROPIC_API_KEYGet key
Click Create key. It starts with sk-ant- and is shown only once
What changed
On November 17, 2026 Anthropic launched linked billing in beta. A customer links their own Claude organization to your app, and then you choose per request who pays: you or that customer. It works on /v1/messages and /v1/chat/completions. The same day Anthropic released Python SDK anthropic 2.10.0 and TypeScript SDK @anthropic-ai/sdk 1.10.0, which add beta support for the billing_policy request parameter and new error codes for linked billing refusals. Both also rename error data models and deprecate the old names.
A customer-billed request needs three things:
- the beta header
anthropic-beta: user-profiles-billing-2026-10-01 - the header
anthropic-user-profile-idwith the customer's user profile ID (uprof_...) - this body field:
"billing_policy": {"type": "billing_policy", "bill_to": "user_profile"}"bill_to": "self", or no billing_policy at all, bills you.
Limits on what you can send:
/v1/messages/count_tokensacceptsbilling_policyand ignores it.- Message Batches can't bill the customer. A batch item with
bill_to: "user_profile"comes backerroredwithinvalid_request_error, and nobody is billed. Other items run normally. - A customer-billed request can't use billable code execution features. The API returns a 400.
- Requests run in your organization: your rate limits, model access, service tier, data retention and encryption keys apply. The customer's ZDR, BAA and CMEK do not. Don't link customers that need HIPAA, FERPA or CMEK coverage for this usage.
