Anthropic Lets SaaS Customers Pay for Claude Without Sharing API Keys

Anthropic launches linked billing in beta, letting customers approve third-party platforms like Linear, Factory, and Ramp without handing over API keys.

·
·
·
Anthropic Lets SaaS Customers Pay for Claude Without Sharing API Keys
Read4 min
TypeNews
TopicApi · Infra
  • Anthropic launched linked billing in beta, replacing API key sharing with an OAuth-style approval flow.
  • Customers approve a link to third-party platforms, which bill Claude usage back to the customer's org.
  • Launch partners include Linear, Factory, Ramp, Warp, Asana, ClickHouse, Railway, Tines, Mintlify, and more.
  • Per-platform spend limits, Console visibility, and unlink-anytime controls are built in.
  • Customers can draw down existing Anthropic commitments or pay as they go across any linked platform.
  • Org-level settings like IP allowlists and encryption keys don't carry over to linked platform requests.

Anthropic has launched linked billing in beta on the Claude Platform. The feature lets customers authorize a third-party product to charge Claude usage to their Anthropic organization through a hosted approval flow, without giving the vendor a customer API key.

Many Claude-powered products use a bring-your-own-key model that requires customers to copy a reusable credential into the vendor’s settings. Linked billing reduces that secret exposure, adds centralized spending controls, and allows supported products to draw from the customer’s contracted Anthropic commitment.

Linked billing carries no additional feature fee. Customers use existing committed spend or pay standard Claude API rates. Both the third-party platform and the customer need Claude Platform organizations, and the vendor must support the feature.

The beta opens with 18 integrations

  • Asana
  • ClickHouse
  • Factory
  • Gumloop
  • Harness
  • Higgsfield AI
  • Kilo Code
  • Linear
  • Mintlify
  • Niteshift
  • Omni
  • OpenArt
  • Railway
  • Ramp
  • Runlayer
  • Tessera
  • Tines
  • Warp

Customer keys stay home

An Anthropic API key is a bearer credential: anyone holding it can make requests billed to the issuing organization. A vendor accepting customer keys must store, encrypt, restrict, monitor, and rotate them. Customers must also replace keys after suspected exposure or personnel changes.

With linked billing, an authorized user connects the customer’s Anthropic organization directly to the supported platform. Customer API keys remain inside the customer’s organization, and Anthropic manages the billing relationship through an approval that the customer can revoke.

From approval to charge

  1. Connect: The platform opens an Anthropic-hosted authorization flow for the customer.
  2. Approve: A Console user with an Owner, Admin, or Billing role authorizes the link. The same role requirement applies to individual developer organizations and larger teams.
  3. Set limits: The customer applies a monthly limit for that platform or uses a default limit shared across linked platforms.
  4. Route charges: For each Claude request, the platform chooses whether its own organization or the linked customer pays.
  5. Monitor or revoke: The customer reviews spending by platform in Console and can unlink the integration at any time.
Claude Console showing linked platforms, spending limits, and access types
Claude Console lists connected platforms alongside their spending controls and access types.

Execution stays with the platform

Requests charged to a customer execute inside the third-party platform’s Anthropic organization. The platform organization’s policies therefore govern request handling. IP allowlists, custom encryption keys, and data-retention settings configured in the customer’s organization remain scoped to requests executed there.

Teams with data-residency, encryption, retention, or network restrictions should evaluate the vendor’s Anthropic configuration separately. Linked billing assigns API charges to the customer’s account; the platform retains the execution environment for those requests.

Platforms shed billing work

Vendors can remove customer-key storage and delegate usage charging to Anthropic. That reduces the infrastructure required for API metering, invoicing, and payment collection while preserving request-level control over which party pays.

Platforms can inspect each linked customer’s request count, token usage, model selection, and cost through Console or the Analytics API. Customers receive a platform-level spending breakdown in their own Console.

Third-party developers add support by creating an OAuth app in Console. The implementation uses Anthropic’s hosted authorization flow and selects the payer for each eligible request.

A portable Claude budget

Linked billing turns an Anthropic organization into a payment account that works across participating products. Companies with contracted Claude spend can apply that commitment to supported coding agents, workflow tools, analytics products, and other SaaS applications instead of managing isolated AI charges with each vendor.

The design applies delegated authorization, familiar from OAuth, to API billing. Customers approve and revoke connections through Anthropic’s interface, and vendors avoid receiving reusable customer API secrets.

Four checks before linking

  • Feature coverage: Confirm which product features use linked billing because the platform can select the payer per request.
  • Policy boundary: Review the platform’s data residency, encryption, retention, and network controls.
  • Spend control: Set a monthly platform limit or an organization-wide default before approving usage.
  • Usage visibility: Reconcile the Console spending breakdown with the vendor’s product-level usage reports.
Trending
  • No trending articles

Comments

avatar

Next Reads