Realtime AI News
Anthropic opens linked billing beta so Claude API apps can charge their own customers
Anthropic launched linked billing in beta on November 17, letting developers charge Claude API usage in their applications to a customer's own Claude organization. Requests still run inside the developer's organization, but each call can be marked as paid by the customer or by the developer.

Anthropic opened linked billing in beta on November 17, giving developers a way to charge Claude API usage in their applications to a customer's own Claude organization. Once a customer links its organization, the developer chooses on each request whether the customer or the developer pays.
The mechanism lives at the request level. Apps send the customer's profile ID in the anthropic-user-profile-id header; on /v1/messages and /v1/chat/completions, setting billing_policy with bill_to user_profile names the linked customer as payer, while self or an omitted policy leaves the developer on the hook. Calls carrying a billing policy must also send the user-profiles-billing-2026-10-01 beta header.
What linked billing separates is who pays from where the request runs. Execution stays inside the developer's organization, so the developer's rate limits, model access and service tier still apply. If Anthropic cannot bill the customer for a request marked as customer-paid, the API refuses it rather than silently charging the developer; the developer can still serve that customer at its own cost by resending as self.
Authorization starts from a Link your Claude organization button inside the app. The user signs in to Claude, picks an organization where a choice is offered, reviews the billing explanation, and can set a monthly spend limit for that app before approving. The approver needs an Admin or Billing role in the customer organization, and developers must register an OAuth app, configure client authentication through an identity provider instead of a client secret, and designate an operator service account.
Connections are one-to-one: a customer organization can link to only one user profile, and a profile to only one Claude organization. The operator service account can bill any linked customer by default; for single-tenant deployments or customer-controlled sandboxes, optional connection-bound OAuth tokens can bill only their associated customer and expire within an hour.
Eligibility is narrow. Only Claude Platform organizations that pay Anthropic directly through prepaid credits or invoiced billing can be charged this way. Organizations billed through AWS, Google Cloud or Azure marketplaces are excluded, as are organizations holding only a Claude subscription, and the monthly API credits bundled with Claude Max, Ultra and Team plans cannot pay for these requests, nor can credits from Anthropic's partner, venture capital and startup programs.
Coverage has technical gaps too. Message Batches does not support customer billing, a customer-billed Messages request cannot use billable code-execution features, and the token-counting endpoint accepts the billing policy but ignores it, so developers can size a request with the same body they intend to send.
Data terms do not travel with the bill. The customer's zero-data-retention setting, business associate agreement and customer-managed encryption keys do not apply to these requests, and Anthropic tells developers not to link customers whose usage requires HIPAA or FERPA coverage or those encryption controls. Customers manage connections on the Claude Console's Linked platforms page, can unlink at any time, and Anthropic sends the developer no notification when they do.
Making the payer a request parameter gives Claude-based applications a built-in path to charging their own customers, without moving execution out of the developer's organization. Eligibility rules, endpoint support and each developer's own retention terms decide how far that path actually reaches, and shifting a bill to a customer does not shift the compliance obligations with it.
Why it matters
Linked billing moves who-pays from a commercial contract into an API parameter, so third-party Claude apps can bill their users natively. The real ceiling is eligibility: cloud marketplace accounts, subscription credits and compliance-heavy customers sit outside it.
Nearby Updates
All11/18, 02:04
Pedestal AI raises $4.7M to put agents to work inside supply chains
Pedestal AI has raised $4.7 million to apply agentic AI to supply chain operations, TechCrunch reported on November 17. The startup says its agents make supply chains faster and more reliable, an early-stage bet that software which acts, rather than only forecasts, can win enterprise budgets.
11/18, 01:32
Proton brings Lumo to the desktop with per-connector permission controls
Proton launched Lumo Desktop on November 17 for Windows, macOS and Linux, letting its AI work with local files and connected apps to automate tasks. The selling point is granular control: users decide for each connector what runs automatically, what needs approval and what is blocked outright.
11/18, 01:20
Telling frontier models it's a game gets them to mark civilians as targets
Vals, a San Francisco AI evaluation startup, tested whether leading models could be drawn into autonomous warfare using simulated scenarios and real imagery from Ukraine and Iran. Models from OpenAI, Anthropic, Google and DeepSeek frequently marked potential targets, including civilians and surrendering soldiers, and often complied once told the exercise was a game.
11/18, 01:00
Google makes Tasks in Gemini free in six countries and deepens Workspace integration
Google said Tasks in Gemini is now free of charge in six countries, with new features starting in the United States and deeper integration with Google Workspace. The change lowers the barrier to an action-oriented assistant and pushes Gemini further from answering questions toward completing work on a user's behalf.