Anthropic said on November 17, 2026, that linked billing is available in beta on the Claude Platform. In a product update, the company said “Third-party platforms, such as coding agents and workflow automation tools, can let their end customers pay for Claude API usage without sharing an API key.” Anthropic describes the feature as “a more secure alternative to sharing API keys,” and says platforms get “a simpler, more secure way to offer Claude.” The Next Web’s Ana Maria Constantin reported the same day that Anthropic had launched linked billing in beta.

#What changed?

Anthropic says that paying for Claude API usage on a third-party platform usually means sharing an API key. With linked billing, “customers link their Claude Platform organization instead, and usage is billed directly to it.” The company says: “No API key changes hands, so platforms have no customer keys to store, encrypt or rotate, and customers’ API keys never leave their organization.”

A help center article says a customer links its Claude Console organization using OAuth instead of pasting in an API key. The platform holds a connection ID, not a key, runs Claude for the customer, and Anthropic bills the customer directly. Platforms can keep offering customer API keys alongside linked billing and move customers over at their own pace.

Anthropic says it hosts the approval flow and the billing, so there is no metering or invoicing for platforms to build. Platforms send requests, and Anthropic bills the end customers directly. Platforms can decide on each request whether the platform or the end customer pays. Claude Platform documentation says: “If a request you mark for the customer can’t be billed to them, the Claude API refuses it rather than billing you.” The help center says platforms see each customer’s usage and what it costs them, and that they never see what the customer actually pays.

According to the help center, linked billing covers the /v1/messages and /v1/chat/completions endpoints. Release notes dated November 17, 2026 say platforms set billing_policy on each of those requests to choose who pays, and that the feature launched in beta with the user-profiles-billing-2026-10-01 beta header. The help center says the Message Batches API and Claude Managed Agents “aren’t covered yet,” and that customer-paid requests can’t use billable code execution.

Customers approve each linked platform, set a spend limit, and can unlink at any time, Anthropic says. They can draw down from their existing Anthropic commitment, or pay as they go. An administrator or billing member approves the link. The help center says one approval covers the whole organization, and that the link stays active if the approver leaves. Customers can set a monthly spend limit for each platform, or a default that applies to each one, in the Claude Console. The documentation says a customer can set a monthly spend cap for an app in US dollars (USD), that the cap counts token costs and web search fees at list prices before any negotiated discount, and that the customer’s bill can differ from the amount that the cap counts. Unlinking usually stops new calls within about 10 seconds, the help center says.

The same product update states: “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 documentation adds: “Your customer’s own data arrangements don’t apply to these requests, including zero data retention (ZDR), a business associate agreement (BAA), and customer-managed encryption keys (CMEK).” It also says: “Don’t link customers that need HIPAA, FERPA, or CMEK coverage for this usage.”

Anthropic said platforms that support linked billing include Asana, ClickHouse, Factory, Gumloop, Harness, Higgsfield AI, Kilo Code, Linear, Major, Mintlify, Omni, OpenArt, Niteshift, Railway, Ramp, Runlayer, Tessera, Tines, and Warp. Claude Platform customers can link their organization from any supported platform, and can find platforms that offer linked billing on Claude Marketplace, the company said.

#Who can use it and when?

Linked billing is available in beta as of November 17, 2026, on the Claude Platform. The documentation says a customer can be billed this way only if their Claude Platform organization pays Anthropic directly for its API usage, and that prepaid credits and invoiced billing both count. The help center says: “Linked billing works only for customers whose Claude Console organization is billed directly by Anthropic.”

Customer or plan

What Anthropic’s documentation and help page say

Organizations billed directly by Anthropic

Can be billed this way. Prepaid credits and invoiced billing both count.

Cloud marketplace billing (AWS, Google Cloud, or Azure)

Can’t use linked billing.

Cloud providers (Bedrock, Vertex AI, or Foundry)

Can’t link.

Claude subscription plans (Pro, Max, Ultra, Team, and Enterprise)

Can’t be linked. Monthly API credits that come with Max, Ultra, and Team plans can’t pay for these requests.

Partner, VC, and startup program credits

Aren’t eligible to pay for these requests.

Third-party platforms can add support by creating an app in the Claude Console and following Anthropic’s documentation. A new app starts in testing. Only the test users the platform lists, up to 10, can link it, each with a monthly limit of $50 or less. Unless the platform’s organization has invoiced billing, the platform verifies the app’s domain, and Anthropic reviews the app before it is live.

#How does it compare?

Linked billing is a billing path for third-party apps, not a change to Claude’s subscription plans. Anthropic presents it as an alternative to sharing an API key, and says platforms can keep offering customer API keys alongside the new flow. Anthropic has opened self-hosted Claude Managed Agents in private beta, and the help center says Claude Managed Agents are not covered by linked billing. Spend tools the site has covered, including pooled budgets in Claude Enterprise, are a separate path. Anthropic’s help page says Enterprise and the other Claude subscription plans can’t be linked.

Our analysis: The practical change is who gets billed, and who holds a key. Anthropic attributes a security benefit to that split, calling linked billing “a more secure alternative to sharing API keys.” The same pages are explicit that only billing moves to the customer. Requests run in the platform’s organization, so the customer’s IP allowlists, encryption keys, data retention, zero data retention arrangements, business associate agreements, and customer-managed encryption keys do not apply.

#What is still unclear?

Anthropic has not said when the beta will end, or when the Message Batches API and Claude Managed Agents will be covered. It has not given a date for supporting organizations billed through a cloud marketplace or a cloud provider, or for letting Claude subscription plans link. The documentation says endpoints, parameters, and behavior can change during the beta, and that it might not be suitable for production use. The company has not published prices specific to linked billing. It says usage is billed under the organization’s existing billing terms, and that a spend cap can count a different amount from the customer’s bill, without examples of how those figures can diverge.