Claude adds linked billing for third-party platforms in beta
Claude Platform's linked billing beta lets customers authorize third-party billing without sharing API keys. Linear administrators can approve links, set spending limits and revoke access.

TL;DR
- Claude Platform's linked billing beta lets third-party tools charge a customer's organization without receiving its API key, according to Anthropic's announcement.
- Platforms choose who pays on each request; customers can draw down existing Anthropic commitments or pay as they go, as Anthropic explains.
- Administrators can approve links, set spend limits and revoke access, according to Linear's launch for its cloud coding agent.
ClickHouse is applying linked billing to model calls from SQL. An organization’s approval survives the departure of the administrator who granted it.
OAuth and service accounts
An exposed API key lets its holder make requests on the customer's bill, Anthropic notes. The integration guide describes three platform-side components behind the replacement:
- OAuth app: Registered in Claude Console, with an Anthropic-hosted approval flow requesting the
billing:attributionscope. - Operator service account: The platform's backend authenticates through Workload Identity Federation. Only the app's designated operator service account can send inference requests attributed to its linked customer profiles.
- Customer user profile: A record in the platform's organization identifies the customer. Within one app, each customer organization links to one profile, and each profile links to one organization.
Per-request billing
The welcome safeguard in Anthropic's API guide: a request marked for customer billing is refused if it cannot be charged to that customer, rather than automatically landing on the platform's bill.
The request mechanics are explicit:
- Customer pays: Set
billing_policywithbill_to: "user_profile"and identify the linked customer profile. - Platform pays: Set
bill_to: "self", or omitbilling_policy. This permits platform-funded features alongside customer-funded usage. - Supported inference endpoints:
/v1/messagesand/v1/chat/completions. - Token counting:
/v1/messages/count_tokensaccepts and ignoresbilling_policy, allowing the same request body to be counted before inference. - Unsupported paths: Message Batches cannot bill the customer. Customer-billed requests using billable code execution return a 400 error.
Spend limits and usage accounting
Warp says linked usage is billed on the organization's existing Anthropic terms. Its integration puts monthly spend limits and unlinking in Claude Console.
Anthropic's launch post specifies the controls and accounting surfaces:
- Approval: A Console user with an Owner, Admin or Billing role authorizes the organization-wide link.
- Budgets: Customers can set a monthly limit for each platform, or a default limit that applies to each one.
- Customer accounting: Console breaks out spend by linked platform.
- Platform accounting: Request counts, token usage and models used are visible per customer in Console or through the Usage and Cost Analytics API, also in beta.
19 launch platforms
The beta's supported platforms are:
- Asana
- ClickHouse
- Factory
- Gumloop
- Harness
- Higgsfield AI
- Kilo Code
- Linear
- Major
- Mintlify
- Niteshift
- Omni
- OpenArt
- Railway
- Ramp
- Runlayer
- Tessera
- Tines
- Warp
Only organizations billed directly by Anthropic qualify, Linear notes. The developer guide excludes organizations billed through AWS, Google Cloud or Azure marketplaces, and accounts with only a Claude subscription plan; ineligible requests return 403 user_profile_not_billable.
Purchased Console credits and invoiced billing can pay for linked usage. Credits from Anthropic's partner, VC and startup programs cannot, according to the same guide.
Platform-side data controls
Requests execute in the third-party platform's Claude organization. The developer guide assigns the configuration accordingly:
- Capacity and access: The platform's rate limits, model access and service tier apply.
- Data handling: The platform's retention settings and encryption keys apply. The customer's zero data retention, business associate agreement and customer-managed encryption-key arrangements do not carry over.
- Network restrictions: Customer IP allowlists do not apply, as the launch announcement also specifies.
Anthropic's guide warns against linking customers that require HIPAA, FERPA or customer-managed encryption-key coverage for this usage.