Independent · Source-cited · No sponsored rankingsSources linked in every article
AIToolRanked
AI News · 5 min read

Claude Linked Billing: No API Key, Customers Set a Spend Cap

Anthropic's linked billing beta lets an app bill Claude API use to the customer's organization. No API key is shared. A subscription plan does not qualify.

RA
· Founder, AIToolRanked
An app window with a chain-link button, a dotted line to a shield holding a chain link, organisation cards with a spend dial and a coin stack, and a faded crossed-out key
On this page

What Anthropic shipped on November 17

On November 17, 2026, Anthropic introduced linked billing in beta on the Claude Platform. The Next Web ↗ reported the launch that day and said it went out in beta on Tuesday, citing Anthropic's release notes. Anthropic's article, Linked billing on the Claude Platform ↗, says it is available in beta. The developer guide is the organization billing connections ↗ doc. Customer steps are in the help centre ↗. The picture above is an original graphic created by aitoolranked. We have not used linked billing.

A third-party platform, a coding agent or a workflow tool, lets a customer pay for Claude API usage without sharing an API key. The customer links a Claude Platform organization. Usage is billed to it. The platform stores no customer key and rotates none. Anthropic hosts the approval screen and the bill. The platform sees each customer's request count, tokens, and models in Console, or through the Usage and Cost Analytics API, which Anthropic marks beta.

Anthropic's article says a Console user with the Owner, Admin, or Billing role approves. The help centre names Admin or Billing. The customer sets a monthly spend limit per platform, or a default, sees spend per platform in Console, and unlinks from the Linked platforms page at any time. Usage draws down an existing commitment or is pay as you go. The docs ↗ say Anthropic does not notify the developer by webhook or email when a customer unlinks. A later customer-billed request is refused with 403 user_profile_not_billable. Anthropic emails the customer's Admin and Billing members on link and on unlink. It sends no email when the platform unlinks the customer from the Console, and it does not guarantee delivery.

Who pays, and who cannot

The docs name the beta header user-profiles-billing-2026-10-01, the header anthropic-user-profile-id, and a billing_policy field. bill_to of user_profile means the customer pays. bill_to of self, or omitting the field, means the platform pays. That is supported on /v1/messages and /v1/chat/completions. /v1/messages/count_tokens accepts the field and ignores it. Message Batches does not support customer billing. A customer-billed request cannot use billable code execution. The API returns 400. If the customer cannot be billed, the request is refused rather than charged to the developer. The docs list a 402 when the organization has no usable credit or has reached a spend limit.

Who paysField
Customerbill_to user_profile
Platformbill_to self, or omit

Requests run in the platform's organization. The customer's IP allowlists, encryption keys, and data retention do not apply, Anthropic's article says. The docs add zero data retention, a BAA, and CMEK, and say not to link a customer that needs HIPAA, FERPA, or CMEK coverage for this usage. Only an organization that pays Anthropic directly qualifies, on prepaid credits or an invoice. An AWS, Google Cloud, or Azure marketplace bill does not, and neither does a subscription-only organization. The help centre also excludes Bedrock, Vertex AI, and Foundry, and it names Pro, Max, Ultra, Team, and Enterprise plans. Monthly API credits with Max, Ultra, and Team cannot pay. The docs say partner, VC, and startup program credits cannot pay either. The help centre says that exclusion is still rolling out.

The help centre says the request that crosses a spend limit is still served, calls already running finish, and the total can end up a little above the limit.

Anthropic's launch list is 19 platforms: Asana, ClickHouse, Factory, Gumloop, Harness, Higgsfield AI, Kilo Code, Linear, Major, Mintlify, Omni, OpenArt, Niteshift, Railway, Ramp, Runlayer, Tessera, Tines, and Warp. Anthropic says to find them on Claude Marketplace. On that page, Tom Moor of Linear says: "Manually copying API keys is inherently insecure."

What people are saying

  • "New: BYOB (Bring your own billing)" — Linear ↗ (@linear)

  • "but Claude Pro/Max/Ultra still doesn't count, only API billing. safer setup, same second bill." — Abdullah ↗ (@abdullah0094)

  • "Platforms should not hold keys or eat usage costs, and customers need a cap they control." — Michael Du ↗ (@mhrdu001)

  • "If you sell AI agents: do you pass usage through to the customer, or eat it and price on outcomes?" — Jaser ↗ (@JaserAkuly)

Reddit was not reachable for this story.

Our take

Link it when the organization already pays Anthropic directly and the app is on the list of 19. Linear, Warp, and Factory are the obvious coding names. The customer sets the cap. The platform does not hold the key. Michael Du's sentence is the product. Jaser's question is the field in the docs: user_profile passes usage through, self means the platform pays.

A chat subscription does not pay this. Abdullah names Pro, Max, and Ultra. The help centre adds Team and Enterprise, plus marketplace billing and Bedrock, Vertex, and Foundry. Prepaid credits or an invoice qualify. The monthly API credits inside Max, Ultra, and Team do not.

Leave HIPAA, FERPA, and CMEK work off it. Those customer controls do not travel with the request, and the request that crosses the cap is still served.

This is not a router, and it is not a fix for stolen keys. Perplexity Orchestrator is one key in front of many models. Hugging Face Inference Providers is a routing change. The key-theft context is MadPot and Google's GTIG note on a Claude Code settings backdoor and LLMJacking. Linked billing removes the habit of pasting a key into someone else's app. Products that still take a key are the Claude Code review and cheaper Claude Code alternatives. The listing is separate: Anthropic's IPO range.

Verdict: Link when the organization pays Anthropic directly, an Admin or Billing user sets a monthly cap, and the work does not need the customer's BAA or CMEK. Skip a subscription-only seat and a marketplace bill. The key stays put. The compliance settings do not.

More from the news desk · About Rai Ansar