claudekit / updates / linked-billing-claude-platform
[ NEW · ]

Linked billing on the Claude Platform — let customers pay for Claude API usage without sharing an API key (beta)

Linked billing is now available in beta on the Claude Platform. Third-party platforms, such as coding agents and workflow automation tools, can let their end customers pay for Claude API usage without sharing an API key. Customers link their Claude Platform organization, and usage bills directly to it. Customers approve each linked platform, set a spend limit, and can unlink at any time.

Official announcement →

This article is a summary based on official documentation.

Overview

Anthropic introduced linked billing on the Claude Platform in beta on November 17, 2026. With linked billing, third-party platforms, such as coding agents and workflow automation tools, can let their end customers pay for Claude API usage without sharing an API key. Customers link their Claude Platform organization, usage bills directly to it, and end customers keep their existing Anthropic billing and set their own spend limits.

Key features

  • No API key changes hands

    When customers share an API key with a platform, the platform has to store, encrypt, and rotate it, and the key leaves the customer’s organization. With linked billing, customers link their organization through a flow that Anthropic hosts, and usage bills directly to it. Platforms don’t store, encrypt, or rotate customer keys, and customers’ keys stay inside their organization. A Console user with an Owner, Admin, or Billing role approves the link.

  • Existing billing and per-platform spend limits

    Customers can draw down from their existing Anthropic commitment, or pay as they go. They can set a monthly spend limit for each platform, or a default that applies to each one, and see spend for each platform in Console. Customers approve each linked platform and can unlink at any time.

  • Platforms choose who pays, per request

    A platform decides per request whether it or the end customer pays. Per the docs, a request to /v1/messages or /v1/chat/completions with the anthropic-user-profile-id header and "billing_policy": {"type": "billing_policy", "bill_to": "user_profile"} bills the customer. bill_to: "self", or omitting billing_policy, means the platform pays. These requests use the beta header user-profiles-billing-2026-10-01.

  • Per-customer usage visibility

    Platforms can view usage per linked customer, including request count, token usage, and models used, in Console or through the Usage and Cost Analytics API (beta). Because Anthropic hosts the approval flow and billing, platforms can launch faster.

Notes

  • Beta — The docs note that endpoints, parameters, and behavior can change during the beta, and that it might not be suitable for production use. The announcement doesn’t list separate pricing.
  • Supporting platforms — At launch: Asana, ClickHouse, Factory, Gumloop, Harness, Higgsfield AI, Kilo Code, Linear, Major, Mintlify, Omni, OpenArt, Niteshift, Railway, Ramp, Runlayer, Tessera, Tines, and Warp. You can find platforms that offer linked billing on Claude Marketplace.
  • The customer’s organization settings don’t apply — 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. The docs add that the customer’s own data arrangements, including zero data retention (ZDR), a business associate agreement (BAA), and customer-managed encryption keys (CMEK), don’t apply, and say: “Don’t link customers that need HIPAA, FERPA, or CMEK coverage for this usage.”
  • Eligible customers — The customer’s Claude Platform organization must pay Anthropic directly for its API usage (prepaid credits and invoiced billing both count). Organizations billed through a cloud marketplace (AWS, Google Cloud, or Azure), and organizations that have only a Claude subscription plan, can’t be billed this way. Some promotional credits can’t pay for these requests, including the monthly API credits that come with Claude Max, Ultra, and Team plans, and credits from Anthropic’s partner, VC, and startup programs.
  • Some API features don’t support customer billing — A request that bills the customer (bill_to: "user_profile") can’t use billable code execution features (the API returns a 400), and Message Batches doesn’t currently support billing the customer.
  • How spend caps work — When a customer’s spend through a platform reaches the cap, the Claude API refuses requests billed to them with a 402 until 00:00 UTC on the first day of the next month, or until the customer raises or removes the cap. The cap counts token costs and web search fees at list prices before any negotiated discount. While an app is in testing, the cap is $50 USD or less.
  • For platform developers — Create an app in Console and follow the linked billing documentation.
§ 4

Frequently Asked Questions

frequently asked
§ 4.1
What is linked billing on the Claude Platform?
Linked billing lets third-party platforms bill their customers' Claude API usage to the customer's own Claude Platform organization. The customer links their organization once through an approval flow that Anthropic hosts, and no API key changes hands.
§ 4.2
Is it available now?
Linked billing became available in beta on the Claude Platform on November 17, 2026. At launch, 19 platforms support it, including Asana, Linear, Ramp, Railway, and Warp, and you can find platforms that offer linked billing on Claude Marketplace.
§ 4.3
Which organizations can pay through linked billing?
A customer can be billed this way only if their Claude Platform organization pays Anthropic directly for its API usage. Prepaid credits and invoiced billing both count. Organizations billed through a cloud marketplace (AWS, Google Cloud, or Azure), and organizations that have only a Claude subscription plan, can't be billed this way.
§ 4.4
How do customers control what a platform spends?
Customers can set a monthly spend limit for each platform, or a default that applies to each one, during linking or later on the Linked platforms page in Console. When spend reaches the cap, requests billed to the customer are refused until 00:00 UTC on the first day of the next month or until the cap is raised or removed. Customers can unlink at any time.
§ 4.5
Do my organization's data retention and ZDR settings apply?
No. 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. The docs add that zero data retention (ZDR), a business associate agreement (BAA), and customer-managed encryption keys (CMEK) don't apply either, and that platforms shouldn't link customers that need HIPAA, FERPA, or CMEK coverage for this usage.
§ 4.6
Where can I find the official announcement?
See the announcement at claude.com/resources/articles/linked-billing-on-claude-platform and the Linked billing docs at platform.claude.com/docs/en/manage-claude/oauth-apps/organization-billing-connections.