Anthropic has introduced linked billing on the Claude Platform in beta, a way for third-party apps to let customers pay for Claude API usage without handing over an API key. Anthropic announced the feature on 17 November 2026 with 19 supporting platforms, including Asana, Linear, Ramp, Tines and Warp.
Quick Take
- What: customers link their Claude Platform organization to an app, and usage is billed directly to them.
- No key sharing: API keys never leave the customer’s organization.
- Controls: monthly spend limits per platform, spend shown per platform in Console, and unlinking at any time.
- For platforms: Anthropic hosts the approval flow and billing, and platforms decide per request who pays.
- Status: beta, available today.
In plain English
Many coding and workflow tools ask you to paste in your own Claude API key so the AI costs go on your bill. That key works like a password. With linked billing, you approve the app once from your Anthropic account, set a spending cap and keep your key private. The app sends requests, and Anthropic bills you directly.
What happened
Anthropic wrote that third-party platforms “can let their end customers pay for Claude API usage without sharing an API key.” Supported platforms today are Asana, ClickHouse, Factory, Gumloop, Harness, Higgsfield AI, Kilo Code, Linear, Major, Mintlify, Omni, OpenArt, Niteshift, Railway, Ramp, Runlayer, Tessera, Tines and Warp. Customers can find them on Claude Marketplace.
Background
Bring-your-own-key setups are common across AI tools, but they push key storage and rotation onto every vendor. Linked billing fits Anthropic’s push to sell Claude through partner platforms as well as directly.
How it works
- Approval: a Console user with the Owner, Admin or Billing role links the organization through Anthropic’s hosted flow, so one link covers the whole team.
- Payment: customers can draw down an existing Anthropic commitment or pay as they go.
- Usage data: platforms see each linked customer’s request count, token usage and models in Console or through the Usage and Cost Analytics API, also in beta.
- Important caveat: requests run in the platform’s organization, so the customer’s own settings, such as IP allowlists, encryption keys and data retention, do not apply.
Why it matters
For companies, AI spend across many tools lands on one Anthropic bill with caps per tool.
For developers of AI apps, there is no metering or invoicing to build and no customer keys to protect.
For security teams, fewer API keys in third-party systems means fewer keys to leak, but data settings follow the platform, not the customer.
What’s still open
- When linked billing leaves beta.
- Whether the data retention gap matters for regulated customers.
- How quickly more platforms adopt it.
Sources
- Anthropic, “Linked billing on the Claude Platform,” 17 November 2026
- Claude Platform documentation, “Linked billing”
- Claude Help Center, “Use your Claude Platform account in a third-party app”
i10x Perspective
Billing plumbing rarely makes headlines, but it shapes who owns the customer. Linked billing keeps the paying relationship with Anthropic even when Claude is used inside someone else’s product. More on our Anthropic company page and in the Enterprise & Work section.






