Anthropic launched linked billing in beta on the Claude Platform on Tuesday, November 17. The feature lets third-party platforms — such as coding agents and workflow automation tools — bill Claude API usage directly to the customer's organization, without the customer having to share an API key.
How it works
The customer links their organization to the platform once, through an approval flow hosted by Anthropic. A user with an Owner, Admin or Billing role approves the connection, which then applies to the whole organization. After that, the platform chooses, request by request, who pays: the linked customer or the platform itself.
Control stays with the customer: they can set a monthly spend limit for each platform, track usage in Console and unlink a platform at any time. Platforms, in turn, can see usage per customer — request counts, tokens and models used — in Console or through the Usage and Cost Analytics API, also in beta.
What changes — and what does not
The change is about billing, not execution: requests keep running in the platform's organization, not the customer's. As a result, the platform's rate limits, model access and service tier still apply, and the customer's organization settings — such as IP allowlists, customer-managed encryption keys and zero data retention — do not apply to these requests. Anthropic instructs developers not to link customers whose usage requires HIPAA or FERPA coverage or those encryption controls.
There are eligibility limits: only Claude Platform organizations that pay Anthropic directly, through prepaid credits or invoicing, can be billed. Organizations billed through AWS, Google Cloud or Azure, and anyone with only a Claude subscription plan, are excluded. Linked billing also does not cover the Message Batches API or billable code execution on customer-paid requests.
Who already offers it
According to Anthropic, 19 platforms already offer linked billing at launch: Asana, ClickHouse, Factory, Gumloop, Harness, Higgsfield AI, Kilo Code, Linear, Major, Mintlify, Omni, OpenArt, Niteshift, Railway, Ramp, Runlayer, Tessera, Tines and Warp. Customers can find the participating platforms on the Claude Marketplace.
The feature arrives in a busy month for the Claude Platform — and for Anthropic itself, which also announced this week that it reached the recursive self-improvement threshold (read Geekiki's update).
Why it matters
Until now, paying for Claude inside a third-party app almost always meant handing over an API key — which works like a password: whoever holds the key can run up charges on the customer's account, and the platform has to keep it safe. Linked billing removes the key from the equation: the connection is approved once, with a spend limit and revocation at any time, and billing goes straight to the customer's organization. For developers, the model also simplifies offering Claude: Anthropic hosts the approval flow and the billing, so the platform does not need to build metering or invoicing of its own.
Image credit: official illustration from the linked billing announcement, by Anthropic.
Fontes
- Linked billing on the Claude Platform (Anthropic)
- Anthropic Launches Linked Billing Beta for Claude API Apps (Unite.AI)
- Tessera Brings Linked Billing with Claude Platform to the Enterprise (Business Wire)
Transparency note: this article was produced with the assistance of artificial intelligence, based on cross-checking public posts on X and sources on the internet, and reviewed against the original sources cited above. We recommend consulting the original sources to confirm the information before making any decision.
By Muse