Source: Anthropic blog — Linked billing on the Claude Platform Type: Product Launch (beta) Product: Claude Platform Published: 2026-11-17
Linked billing lets third-party platforms offer Claude API usage without requiring customers to share an API key. Customers link their Claude Platform organization; usage bills directly to it. Available in beta as of 2026-11-17.
The problem it solves
Paying for Claude API usage on a third-party platform traditionally requires sharing an API key, which works like a password: anyone with the key can make requests billed to the customer, and the platform must store, encrypt, and rotate it securely. This creates security risk on both sides.
How linked billing works
Customers link their Claude Platform organization to the third-party platform via Anthropic’s hosted OAuth flow. After that:
- Usage runs in the platform’s organization and bills directly to the customer’s Claude Platform account
- No API key changes hands
- Platforms have no customer keys to store or rotate
- Customers retain full visibility and control
Requests run under the platform’s organization context — the customer’s organization-level settings (IP allowlists, encryption keys, data retention policies) do not apply to linked requests.
Customer controls
| Control | Details |
|---|---|
| Link once | A Console user with Owner, Admin, or Billing role approves the link for the whole org |
| Spend limits | Set a monthly spend limit per platform, or a default that applies to all |
| Spend visibility | Console shows API spend broken down per linked platform |
| Unlink | Customers can unlink any platform directly from Console at any time |
Platform side
- Platforms see usage per linked customer
- Platforms add support by creating an app in Console and following the linked billing docs
- Customers find linked billing-enabled platforms on Claude Marketplace
Supported platforms at launch
Asana, ClickHouse, Factory, Gumloop, Harness, Higgsfield AI, Kilo Code, Linear, Major, Mintlify, Omni, OpenArt, Niteshift, Railway, Ramp, Runlayer, Tessera, Tines, Warp
Key Takeaways
- Linked billing replaces API-key-sharing with an OAuth-based link between a customer’s Claude Platform org and a third-party platform
- No API key leaves the customer’s organization
- Customers control spend limits and can unlink at any time
- Usage bills to the customer’s existing Claude Platform account; platforms can’t be over-billed
- Beta launched 2026-11-17; find participating platforms on Claude Marketplace
- Relates to: Claude Code on the web (cloud sessions also run in the customer’s org), MCP (alternative integration pattern for giving platforms tool access)