Paper invoices and a calculator on an office desk

Who pays when Claude runs inside 19 other tools?

Who pays for Claude when your team runs it inside another company’s tool? From November 17, 2026, your own Claude organization can pay directly. Linked billing is in beta, and 19 platforms support it at launch. Your firm links once, sets 1 monthly spend cap per app, and stops sharing an API key.

Direct answer: Claude linked billing lets a customer organization pay for Claude usage inside a third-party app. The app chooses the payer on each request. The customer sets a cap in the Claude Console and can unlink the app at any time. Only organizations that pay Anthropic directly for API usage can use it.

A shared API key works like a password that carries your billing with it. Linked billing removes that handover and replaces it with an approval, a cap, and a Console record.

Advertisement

Which 19 platforms support linked billing today?

The launch list holds 19 names, and several sit inside Canadian offices already. Asana, ClickHouse, Factory, Gumloop, and Harness open the list. Higgsfield AI, Kilo Code, Linear, Major, and Mintlify follow. Omni, OpenArt, Niteshift, Railway, and Ramp come next. Runlayer, Tessera, Tines, and Warp close the 19.

A Calgary team running Linear and Ramp has 2 live cases on day 1. A Toronto firm adding Asana, Tines, and Warp has 5. Each linked app gets its own cap, so the count sets your control workload.

The app chooses who pays, request by request, through a billing field on each request. Requests your firm pays for run through 2 endpoints, the messages endpoint and the chat completions endpoint. Batch requests cannot bill your organization, so batch work stays on the app’s account. When a request marked for your organization cannot be billed to it, the request is refused. The cost never slides past your cap.

How does the spend cap work in the Claude Console?

Your firm sets a monthly spend cap for each app in US dollars. The user who links sets the first cap on the approval page. An Admin or Billing member later changes it on the Linked platforms page, which also shows each app’s cost this month.

A default cap can cover every linked app that has no cap of its own. Each app can spend up to that default, and the apps share nothing between them. The per-app cap sits apart from the monthly spend limit for your whole organization. Reaching either limit stops the requests billed to your firm.

When spend through an app reaches its cap, later requests return a 402 error. Refusals last until 00:00 UTC on the 1st day of the next month. Your firm can raise or remove the cap, and a change takes about 1 minute to apply. The smallest cap is $0 USD, which refuses every request billed to your organization.

While an app stays in testing, the approval cap is required and capped at $50 USD. At the brief rate of US$1 to CAD 1.4326, that ceiling equals $71.63 CAD. After an app goes live, the cap becomes optional with no practical maximum. Caps count token costs and web search fees at list prices before any discount, so your final bill can differ from the counted amount. That gap fits the wider warning in Anthropic S-1 risk factors: what Claude buyers should read.

Who cannot use linked billing at all?

One exclusion decides eligibility before any cap conversation starts. Organizations billed through a cloud marketplace cannot be billed this way. That exclusion covers AWS, Google Cloud, and Azure billing routes. Organizations holding only a Claude subscription plan face the same block, and their requests return a 403 error.

Prepaid credits and invoiced billing both count as direct payment, so those firms qualify. A Canadian firm that bought Claude through a marketplace must change its billing route first. Pull the last Claude invoice this week and name the party that billed your firm. If a marketplace name sits on that invoice, linked billing stays closed to you. The same invoice habit sharpens Budget 2026’s AI chapter isn’t for your firm. Two tax lines are.

What happens to your data terms when a request runs in the app?

Requests run inside the app’s organization, under the app’s own settings. The app’s rate limits, model access, service tier, and data retention apply. Your organization’s data arrangements do not travel with the request. Zero data retention cover, a business associate agreement, and customer-managed encryption keys all stay behind, and IP allowlists stay behind too.

For a Canadian firm, that gap lands directly on vendor risk work. PIPEDA duties stay with your firm when client data moves through a vendor tool. Your privacy review must record whose retention rule governed each linked workflow. Firms that need HIPAA, FERPA, or customer-managed key cover should keep those workflows unlinked, and put that line in the vendor file before any team links an app. The discipline matches Small business patching needs a faster clock than the Cyber Centre’s two weeks.

What should a Canadian finance lead do before linking the first app?

List each platform your firm uses, with its current Claude cost per month. Name who holds Admin or Billing rights today, because only those members can approve a link and manage caps in the Console.

Set 1 cap per app, sized from 1 month of real usage per tool. A single default cap across 5 apps hides the tool that burns the budget. Per-app caps show the overrun on the exact line where it happened. The card-limit logic in Wealthsimple Penny asks before it pays. Your card limit sets the damage applies here in full.

Write the unlink step into the vendor file with a named owner. The feature runs under beta header user-profiles-billing-2026-10-01, and endpoints can change during a beta. Link 1 low-risk workflow first and watch 1 full billing cycle.

Recap

Linked billing launched in beta on November 17, 2026, across 19 platforms. Your organization pays directly, sets 1 monthly cap per app, and shares no API key. Marketplace-billed organizations stay excluded, and your data terms stay behind on linked requests.

Before November 30, 2026, run the 3 checks in order: confirm your billing route, set 1 cap per app, and record whose retention rule governs each workflow. Start from the checked figure: 19 platforms, 1 cap per app, and $71.63 CAD as the testing ceiling.

Read Anthropic S-1 risk factors: what Claude buyers should read next for the contract terms behind every Claude bill your firm pays.

Total
0
Shares
Prev
GPT-6.2 Sol costs $2.87 CAD. Regular Chat gets neither model
A close-up of programming code on a computer screen

GPT-6.2 Sol costs $2.87 CAD. Regular Chat gets neither model

GPT-6

You May Also Like