AI Catchup

Anthropic Adds Linked Billing to the Claude Platform

By 5 min read

Anthropic's linked billing beta lets eligible Claude Platform organizations pay directly for supported Claude API requests made by third-party apps, without sharing an API key. Organizations must pay Anthropic directly for API usage, not through a cloud marketplace or a subscription-only plan. Admin or Billing members approve each link.

Anthropic has put linked billing for the Claude Platform into beta. It lets an eligible customer authorize a supported third-party app to bill selected Claude API requests to the customer's Anthropic organization, without sharing an API key. Eligibility requires direct billing by Anthropic for API usage, through prepaid balance or invoicing; marketplace-billed organizations and organizations using only a Claude subscription plan are excluded. (Claude Platform billing guide, Anthropic Help Center)

Key Takeaways

Linked billing is a beta for organizations that pay Anthropic directly for API usage. For supported API requests, the app's operator credentials can choose whether the linked customer or app pays while operator-only tokenless billing is enabled, which is the default. If that mode is disabled, customer-billed requests must use a connection-bound token that can bill only its linked customer. Customer organization controls do not transfer to the app's organization. (Claude Platform billing guide, Anthropic Help Center)

  • Eligibility: Organizations must pay Anthropic directly for API usage; cloud-marketplace billing and subscription-only accounts are excluded. (Claude Platform billing guide, Anthropic Help Center)
  • Approval: Only a Console Admin or Billing member can approve the connection; those roles can also unlink it through Console. The app may offer an in-product unlink option, and the app team can unlink it from its side. (Anthropic Help Center)
  • Supported requests: Customer billing covers Messages and Chat Completions, not Message Batches or billable code execution in Messages; failed customer billing does not fall back to app billing. (Claude Platform billing guide)
  • Spend: A cap of USD $50 or less is required for a new link or cap change while the app is in testing, in review, or not approved. If a live app returns to review, existing links and saved caps remain; caps are otherwise optional once live. A limit-crossing or in-flight request may still complete. (Claude Platform billing guide, Anthropic Help Center)
  • Data boundary: Requests run in the app's organization, so customer organization controls and protections do not carry over. (Anthropic Help Center)

For supported Claude API requests, the app's operator credentials can bill the linked customer or cover the cost itself while operator-only tokenless billing is enabled, which is the default. If the app disables that mode, customer-billed requests must use that customer's connection-bound access token; the token can bill only its own customer. Customer billing is supported for Messages and Chat Completions requests, but not Message Batches or billable code execution in Messages. If a request marked for customer billing cannot be billed to that customer, the API refuses it rather than falling back to app billing. (Claude Platform billing guide)

Anthropic says app operators can see per-customer request counts, token usage, and models in Console or through the beta Usage and Cost Analytics API. Linked usage is billed to the customer's prepaid balance or invoice, while an app may separately charge for its own subscription. (Anthropic's linked billing announcement, Anthropic Help Center)

Approvals and spend limits

Only a Console user with the Admin or Billing role can approve a connection. Those users can unlink it through Console; the app may also provide an in-product unlink option, and the app team can unlink it from its side. One approval covers the organization, and an organization can connect once per app. The link belongs to the organization rather than the approving employee, so it remains active if that employee leaves. (Anthropic Help Center, Claude Console roles and permissions)

For a new link or cap change made while an app is in testing, in review, or not approved, the cap must be USD $50 or less. A live app sent back to review keeps existing links and saved caps. Caps are otherwise optional once live; a default applies separately to apps without their own cap. A limit-crossing request and calls already in flight may complete, so the final amount can exceed the cap. (Claude Platform billing guide, Anthropic Help Center)

Supported platforms

Anthropic lists Asana, ClickHouse, Factory, Gumloop, Harness, Higgsfield AI, Kilo Code, Linear, Major, Mintlify, Niteshift, Omni, OpenArt, Railway, Ramp, Runlayer, Tessera, Tines, and Warp as supporting linked billing at launch. The company says platforms can add support by creating an app in Console and following its linked-billing documentation. (Anthropic's linked billing announcement)

Review the organization and data boundary

Linked requests run in the app's organization, not the customer's. The customer's organization settings, including data retention controls, encryption keys, and BAA coverage, do not apply to those requests. Anthropic says not to link customers that need HIPAA, FERPA, or CMEK coverage for this usage. (Claude Platform billing guide, Anthropic Help Center)

Related coverage

Sources

Frequently Asked Questions

Which organizations are eligible for linked billing?

The customer organization must pay Anthropic directly for API usage, either through prepaid balance or invoicing. Organizations billed through AWS, Google Cloud, or Microsoft Azure marketplaces, and organizations using only a Claude subscription plan, are not eligible. ([Claude Platform billing guide](https://platform.claude.com/docs/en/manage-claude/oauth-apps/organization-billing-connections), [Anthropic Help Center](https://support.claude.com/en/articles/18467148-use-your-claude-platform-account-in-a-third-party-app))

Which Claude requests can be billed to a linked customer?

Customer billing is supported for Messages and Chat Completions requests, but not Message Batches or billable code execution in Messages. If a request marked for customer billing cannot be charged to that customer, the API refuses it rather than charging the app. ([Claude Platform billing guide](https://platform.claude.com/docs/en/manage-claude/oauth-apps/organization-billing-connections))

Who can approve or unlink a billing connection?

Only Console users with the Admin or Billing role can approve a connection; they can unlink it through Console, and the app may provide an in-product option or unlink it from its side. One approval applies to the organization, and an organization can connect once per app. ([Anthropic Help Center](https://support.claude.com/en/articles/18467148-use-your-claude-platform-account-in-a-third-party-app))

Are spend caps exact, and do customer data controls apply?

For a new link or cap change while an app is in testing, in review, or not approved, the cap must be USD $50 or less. A live app sent back to review keeps existing links and saved caps; caps are otherwise optional once live. Limit-crossing or in-flight requests may exceed the cap. Customer data controls do not apply in the app's organization; Anthropic says not to link customers needing HIPAA, FERPA, or CMEK coverage. ([Claude Platform billing guide](https://platform.claude.com/docs/en/manage-claude/oauth-apps/organization-billing-connections), [Anthropic Help Center](https://support.claude.com/en/articles/18467148-use-your-claude-platform-account-in-a-third-party-app))

Get the weekly AI Catchup

Tools, practices, and what matters, in your inbox every week.