Anthropic adds direct Claude billing for outside tools without shared API keys
The beta gives customers platform-by-platform spending controls. Requests still run in the outside platform’s organization, not the customer’s.
Loading page…
The beta gives customers platform-by-platform spending controls. Requests still run in the outside platform’s organization, not the customer’s.
Listen to this story
Anthropic's linked billing beta lets supported Claude tools charge a customer's existing Anthropic organization without receiving its API key. Customers can keep their current spending commitment or pay as they go, while tool developers avoid handling customer credentials and billing those requests themselves. The key limitation is that requests run in the platform's organization, so the customer's Anthropic security settings do not carry over. Availability therefore depends on supported integrations and customers approving access for their organization.
An Owner, Admin, or Billing user approves a connection once for the organization; customers can set per-platform spending limits and unlink tools in Console.
Customer IP restrictions, encryption-key settings, and data-retention rules do not apply to requests running in a third-party platform's organization.
Platforms can choose whether they or the linked customer pays for each request, and can inspect customer-level request, token, and model usage.
Anthropic launched linked billing in beta on November 17, 2026, letting customers pay for Claude inside supported third-party tools without handing over an API key. The connection charges their existing Anthropic organization directly. Customers gain a way to authorize spending separately from sharing the credentials normally used to access Claude.
Using Claude’s developer service through an outside platform usually involves supplying an API key, Anthropic says. That key works like a password: whoever holds it can send requests charged to the customer. The outside platform must therefore protect the key while using it to provide its service.
Linked billing replaces that handoff with an approved connection between organizations. The platform sends requests, while Anthropic bills the linked customer directly. Because no customer API key changes hands, the platform has no customer key to store, encrypt or rotate. Anthropic hosts both the approval process and the billing, rather than requiring the platform to build usage metering and invoicing for those charges.
The important boundary is where the requests run. Anthropic says they execute in the third-party platform’s organization, not the customer’s. As a result, customer organization settings—including restrictions on allowed IP addresses, encryption keys and data retention—do not apply. Linking the bill does not carry those settings into the outside tool.
Authorization happens through an Anthropic-hosted flow. A Console user with an Owner, Admin or Billing role approves the connection once for the whole organization. Customers can use an existing Anthropic spending commitment or pay as they go, keeping the billing relationship they already have rather than supplying a separate key to each supported service.
For tool developers, linked billing is not an all-or-nothing decision about passing costs through. A platform can choose who pays on each request: itself or the linked customer. That lets it cover selected features while charging other Claude usage directly to the customer, with the choice made by product or instance.
Platforms also retain visibility into usage by linked customer. Console shows request counts, token usage—the units used to measure model input and output—and which models were used. Developers can retrieve those details programmatically through the beta Usage and Cost Analytics API, giving them a way to inspect customer activity even when Anthropic handles the customer’s bill.
Anthropic lists launch supporters including Asana, ClickHouse, Factory, Gumloop, Linear, Railway, Ramp, Tines and Warp. Customers can start the connection from a supported platform and find participating tools through Claude Marketplace. Other platform developers can add support by creating an app in Console and following Anthropic’s integration documentation; the service is available now in beta.
Loading discussion...
Join the conversation
Explain whether that should be a requirement or a customer choice.
Be the first to share a perspective or an experience.
Reader comments
Newest comments first. Replies stay oldest first.