On November 17, 2026 (with @ClaudeDevs announcing on X at 02:00:53 Asia/Shanghai on November 18, 2026), Anthropic introduced linked billing in beta on the Claude Platform—a billing and authorization mechanism rather than a new model release—enabling customers to pay for Claude API usage inside third-party tools using their existing Anthropic billing without sharing API keys.

Image source: Anthropic (https://claude.com/resources/articles/linked-billing-on-claude-platform).
How Linked Billing Works & Organization Boundary
**Direct Customer Billing, Spend Caps & Per-Request Control: **With linked billing, a customer's API keys never leave their organization. Third-party platforms make API requests on the customer's behalf while Anthropic bills the customer's existing commitment or pay-as-you-go balance directly. Platforms can choose per request whether the platform or customer pays and inspect per-customer requests, tokens, and models in Console or the Usage and Cost Analytics API (beta). On the customer side, an Owner, Admin, or Billing user approves the link once for the organization, sets per-platform or default monthly spend caps, tracks spend in Console, and can unlink at any time.
**Data & Security Policy Scope: **Anthropic explicitly notes that requests run in the platform's organization, so settings in the customer's organization—such as IP allowlists, encryption keys, and data retention—do not apply.
Supported Launch Platforms
**19 Platforms Supported at Beta Launch: **Supported platforms listed at launch are Asana, ClickHouse, Factory, Gumloop, Harness, Higgsfield AI, Kilo Code, Linear, Major, Mintlify, Omni, OpenArt, Niteshift, Railway, Ramp, Runlayer, Tessera, Tines, and Warp. Platforms can register apps in Console, and customers can link from supported tools or browse them in the Claude Marketplace.
