Home / Blog / Linked billing on the Claude Platform news update
Tech News

Linked billing on the Claude Platform news update

Anthropic launched linked billing on the Claude Platform in beta, allowing 19 launch partner tools to charge Claude API usage without sharing customer keys.

By Dillip Chowdary • Nov 19, 2026 • Source: Claude Blog

Linked billing on the Claude Platform news update
Image: Claude Blog

At a glance

Product
Claude Platform linked billing
Release stage
Public beta
Pricing model
Existing Anthropic commitment or pay-as-you-go
Initial partners
19 third-party developer platforms
Spend limits
Custom monthly ceiling per platform or default limit
Execution scope
Runs in platform organization; customer policies excluded

Anthropic launched linked billing on the Claude Platform in beta, allowing third-party tools such as coding agents and workflow automation suites to let end customers pay for Claude API usage without sharing API keys. According to Claude Blog's report, customers link their existing Claude Platform organization directly to partner software, preserving established billing relationships while setting custom monthly expenditure limits. The architecture eliminates the need for external software platforms to store, encrypt, or rotate customer API secrets.

This report details the technical mechanisms, administrative controls, platform telemetry options, and ecosystem partnerships powering the new billing architecture for software providers and enterprise clients. Engineering leads, security officers, and product managers can evaluate how the hosted authorization protocol shifts credential risk away from external platforms while maintaining central accounting visibility.

01Credential exposure and direct organization links

Third-party software providers previously required end customers to generate and hand over static API keys to run models. Because API keys operate like shared passwords, external tools had to store, encrypt, and periodically rotate sensitive secrets to prevent unauthorized access. Any party possessing the credential could generate downstream inference calls billed to the customer account.

Linked billing replaces credential exchanges by allowing customers to link their Claude Platform organization directly to third-party tools. API keys never depart the boundary of the customer organization, which removes key management chores entirely for external platforms. Organizations retain direct account ownership while granting designated software platforms permission to request model inferences.

FeatureAPI key sharingLinked billing
Credential storagePlatform stores and encrypts secretNo customer keys stored or handled
Account custodyKey leaves customer perimeterOrganization stays with customer
Revocation pathManual key deletion or rotationInstant console unlinking anytime

02Hosted metering and flexible cost routing

Software providers can launch generative features rapidly because Anthropic manages the hosted connection workflow and underlying billing logic. Engineering teams no longer need to design custom metering systems, tracking infrastructure, or recurring invoicing pipelines before rolling out Claude-driven capabilities. Platforms simply dispatch API requests while Anthropic calculates usage and charges linked customer accounts directly.

Platforms gain granular accounting through the Anthropic Console alongside programmatic telemetry delivered by the beta Usage and Cost Analytics API. System administrators can inspect request frequencies, aggregate token volumes, and specific model choices for every connected customer account. This reporting gives developers precise operational visibility across their entire multi-tenant footprint.

Architects can also configure financial liability on an individual request basis between the platform and the client. A platform can choose to absorb operational expenses for entry-tier features while redirecting intensive production workloads to the customer balance. This dynamic allocation gives providers complete control over pricing structures across different product tiers and customer instances.

03Administrative spend ceilings and tenant isolation

Advertisement

Tech Pulse Daily

Get tomorrow's pulse first

Join engineers who read Tech Pulse before stand-up. Free, weekday mornings.

Account linking applies across entire teams once authorized by a Console member assigned the Owner, Admin, or Billing role. Customers draw inference funding directly against existing prepaid Anthropic commitments or settle through standard pay-as-you-go billing schedules. This structure standardizes deployment routines across solo developer workspaces and enterprise-grade corporate instances.

Central administrators can enforce dedicated monthly budget ceilings for individual platforms or define a uniform spending limit across all connected services. The Anthropic Console tracks cumulative financial expenditure by vendor and allows administrators to sever platform integrations immediately with a single click. These guardrails prevent unexpected cost surges across downstream developer tools.

Note: Requests run in the platform's organization, so settings in the customer's organization, such as IP allowlists, encryption keys, and data retention, don't apply. Because executions occur within platform runtime boundaries, customers must recognize that their own corporate security parameters do not govern third-party workspaces. External providers enforce their own technical boundaries while consuming customer billing resources.

04Launch partners and integrated developer platforms

Nineteen enterprise platforms rolled out linked billing support at launch to streamline developer workflows and billing administration. The initial deployment group includes Asana, ClickHouse, Factory, Gumloop, Harness, Higgsfield AI, Kilo Code, Linear, Major, Mintlify, Omni, OpenArt, Niteshift, Railway, Ramp, Runlayer, Tessera, Tines, and Warp. These providers incorporate Claude across cloud coding agents, database analytics, automated workflows, and terminal environments.

Partner engineering teams reported notable security and operational improvements after eliminating manual credential management. Linear enables one-click committed spend on its cloud coding agent, while Ramp routes queries through Ramp Router without credential handoffs. Railway GM Cody De Arkland noted that developers using Railway Agent can focus on building and deployment rather than manually maintaining API keys.

Enterprise workflow tools also integrated linked billing to accelerate model adoption across diverse departments. Asana connects customer commitments to AI Studio and AI Teammates, while Harness supports linked usage inside Cosmos. Tessera CTO Anirudh Sriram confirmed that enterprise clients now leverage Claude organizations with no new keys to track across internal systems.

05Console onboarding procedure and marketplace discovery

Anthropic launched linked billing in public beta across the Claude Platform with dedicated integration paths for developers and customers. Platform developers integrate the service by establishing an application profile inside the Anthropic Console and adhering to documentation guidelines. Once verified, third-party software products can request billing connections from enterprise users during initial product configuration.

  1. Application creation Register a developer application profile within the Anthropic Console.
  2. Workflow implementation Implement the hosted authorization flow using documentation specifications.
  3. Customer discovery Connect end user accounts through software prompts or Claude Marketplace.
  4. Billing authorization Authenticate the connection via an authorized organization administrator.

Subscribers can discover compatible software integrations directly through Claude Marketplace or initialize connections from within supported partner applications. Billing administrators retain the freedom to audit connected tools, adjust monthly budget allocations, and terminate vendor permissions at will. The hosted mechanism delivers a unified bridge between third-party AI software and underlying platform commitments.

Frequently asked questions

What is linked billing on the Claude Platform?

Linked billing is a beta feature that lets third-party software platforms bill Claude API usage directly to a customer's Anthropic organization. Customers pay through their own account and set spending caps without sharing API keys.

Who can authorize linked billing for an organization?

A user with an Owner, Admin, or Billing role inside the Anthropic Console must approve the platform link. Once approved, the connection applies across the entire organization.

Do customer security settings apply to requests made via linked billing?

No. Because requests run within the platform's organization, customer organization settings like IP allowlists, encryption keys, and data retention rules do not apply.

How can platforms track token usage and costs for linked customers?

Platforms can view customer request counts, token volumes, and model choices directly in the Anthropic Console. They can also access this telemetry programmatically through the beta Usage and Cost Analytics API.

Sources

Dillip Chowdary

Author

Dillip Chowdary

Writes Tech Bytes coverage of AI, engineering, and the tools that actually ship. Editor of Tech Pulse Daily.

Related on Tech Bytes

Advertisement

5-min tech signal

Weekday briefing for engineers who skip the noise.

No spam · Unsubscribe anytime

Advertisement

✈️ CareerPilot

Your AI job-search copilot

Match your resume against live Ashby, Greenhouse & Lever openings — fit scores, job-specific resume optimization and email alerts.

Find matching jobs →

Free Tools

Browse all tools →