Claude linked billing explainer with the official Claude spark icon: your users pay Claude, not your app

Can You Sell a Claude App Without Paying the Token Bill? What Claude Linked Billing Changes

Short answer: Claude linked billing lets your app send Claude API usage straight to your customer’s own Anthropic bill, so you can sell a Claude-powered tool without paying for every token your users burn. It is in beta, Anthropic takes no cut of what you charge and pays you nothing either, and it only works for customers whose Claude organization pays Anthropic directly for the API. The main alternative, asking users to paste an API key, is what this replaces.

Key points

  • Anthropic hosts the approval flow and the billing, so there is no metering or invoicing for you to build.
  • You decide on every request who pays: the customer (bill_to: "user_profile") or you (bill_to: "self").
  • Customers set a monthly spend cap in whole US dollars for your app and can unlink at any time. Anthropic sends you no webhook when they do.
  • Only organizations on prepaid credits or invoiced API billing qualify. Subscription-only accounts and organizations billed through AWS, Google Cloud or Azure are refused.
  • Message Batches and billable code execution cannot be billed to the customer yet, so those stay on your bill.
  • Launch partners include Linear, Warp, Railway, Ramp, Asana, Gumloop, Factory, Mintlify and Kilo Code.

What is Claude linked billing?

It is a new option on the Claude Platform built on Claude Platform OAuth. You add a “Link your Claude organization” button to your product. A customer with the Admin or Billing role signs in to Claude, picks a spend limit and approves your app. From then on, your back end can mark requests for that customer, and Anthropic charges them at list price against their own prepaid balance or invoice.

The requests still run inside your organization. Your rate limits, model access, service tier and data retention apply, not the customer’s. Anthropic’s pitch is mostly security: no customer API keys to store, encrypt or rotate. If you have ever worried about keys leaking, our breakdown of how Claude Code saved secrets to GitHub shows how easily that goes wrong.

How does Claude linked billing help you make money?

It does not pay you anything directly. There is no revenue share and no marketplace payout. What it changes is your margin. Today most indie builders pick one of three models, and each has a cost problem:

Model Who pays for Claude tokens What you build Main risk
Resell usage with a markup You, then you bill the customer Metering, invoicing, usage limits A few heavy users can wipe out your margin
Bring your own API key The customer Secure key storage and rotation You hold keys that work like passwords
Claude linked billing The customer, billed by Anthropic OAuth link button and request flag Only works for direct API customers

With linked billing, the price you charge for your product, a seat fee, a flat plan or a one-off license, is no longer eaten by inference. You can also mix: cover cheap features yourself with bill_to: "self" and pass long agent runs to the customer. Anthropic also says customers can find platforms that support linked billing on Claude Marketplace, which is a small discovery channel on top.

Realistic expectations: Anthropic and its launch partners have published no figures on revenue or conversion from this feature, so treat any income claim you see as unproven. It is a cost and trust lever, not an income stream. Builders who already sell agents or APIs, as covered in our guides on selling AI agents on the new app stores and selling APIs to AI agents with x402, get the most from it.

How do you set up Claude linked billing?

  1. Create the OAuth app. An Admin opens OAuth apps in the Claude Console, clicks Create, adds a name and redirect URI, and selects “Bill and link to organizations”. Set the name, homepage and logo on the Appearance tab.
  2. Set up client authentication. Anthropic issues no client secrets. Your back end proves its identity with a signed client assertion (a private_key_jwt variant) from an identity provider you register.
  3. Create your back end’s identity so it can call the Claude API on behalf of linked customers.
  4. Add the link button. The customer signs in, sets a spend cap and approves. You exchange the returned code for the connection.
  5. Flag paid requests. Add billing_policy with bill_to: "user_profile" to /v1/messages or /v1/chat/completions, plus the anthropic-user-profile-id header and the billing beta header named in the docs.
  6. Publish. Until the app is live, only people on your Test users list can link. Publishing needs a DNS TXT record proving you own the app’s domain, which can take up to 48 hours, then a review by Anthropic. Organizations with invoiced billing skip both.

What are the costs and risks?

  • Small eligible audience. Many Claude users only have a Claude subscription. They get a 403 user_profile_not_billable, so you still need your own billing for everyone else.
  • Some credits cannot pay. The monthly API credits bundled with Max, Ultra and Team plans, plus credits from Anthropic’s partner, VC and startup programs, are excluded.
  • Refusals, not fallbacks. When a customer hits their cap or runs out of credit, the API returns a 402 that is not retryable. Anthropic does not silently bill you, so your product needs a path: pause, warn, or resend with bill_to: "self" at your own cost.
  • Compliance gap. The customer’s zero data retention, BAA and customer-managed keys do not carry over. Anthropic says not to link customers that need HIPAA, FERPA or CMEK coverage.
  • Beta terms. Anthropic says endpoints and behavior can change and it “might not be suitable for production use”. If the review rejects your app, you cannot resubmit yourself.
  • Rules on what you bill. You may bill a customer only for requests they direct you to make, never for your own background usage.

Pricing still follows Anthropic’s list rates, so model choice matters. Our coverage of Claude Haiku 5.5 pricing is a useful reference when deciding which features to push to the customer’s bill.

Who should use Claude linked billing?

It suits B2B developer tools, coding agents, workflow automation and data products sold to teams that already buy the Claude API directly, which is exactly the launch partner list. It is a poor fit for consumer apps, students, or customers on cloud marketplace billing. Our take: if your buyers are engineering teams with an Anthropic invoice, add it now and price your product on value, not tokens. If your buyers are individuals on a Claude subscription, keep your current model and watch whether Anthropic widens eligibility.

Sources

Leave a Comment

Your email address will not be published. Required fields are marked *