Comment by paxys
1 day ago
I don't see how they can get more clear about this, considering they have repeatedly answered it the exact same way.
Subscriptions are for first-party products (claude.com, mobile and desktop apps, Claude Code, editor extensions, Cowork).
Everything else must use API billing.
The biggest reason why this is confusing is the Claude Agent SDK[0] will use subscription/oauth credentials if present. The terms update implies that there's some use cases where that's ok and other use cases (commercial?) where using their SDK on a user's device violates terms.
[0] https://platform.claude.com/docs/en/agent-sdk/overview
Had the same question, comment below quotes their docs saying Agent SDK using oAuth token is also not allowed.
It doesn't quote their docs, it quotes the page this post is about.
The SDK is Claude Code in a harnesss, so it works with your credentials the same way CC does.
But they're stating you can only use your subscription for your personal usage, not someone else's for their usage in your product.
I honestly think they're being short sighted not just giving a "3rd party quota" since they already show users like 4 quotas.
If the fear is 3rd party agents screwing up the math, just make it low enough for entry level usage. I suspect 3rd party token usage is bi-modal where some users just need enough to kick tires, but others are min-maxing for how mamy tokens they can burn as if that's its own reward
How can they be clearer that the Agents SDK is not allowed?
> OAuth authentication (used with Free, Pro, and Max plans) is intended exclusively for Claude Code and Claude.ai. Using OAuth tokens obtained through Claude Free, Pro, or Max accounts in any other product, tool, or service — including the Agent SDK — is not permitted and constitutes a violation of the Consumer Terms of Service.
1 reply →
I agree, it'd actually be great if they did give maybe $5 or $10 worth of API tokens per month to max subscribers, since they're likely to be the most likely to actually build stuff that uses the Claude APIs.
I built a quick thing to download YouTube videos and transcribe them using with whisper, but it kind of feels clunky to summarize them using the claude CLI, even though that works.
1 reply →
> not someone else's for their usage in your product.
what if the "product" is a setup of documents that concisely describe the product so that a coding agent can reliable produce it correctly. Then the install process becomes "agent, write and host this application for the user's personal use on their computer". Now all software is for personal use only. Companies released these things and, like Frankenstein, there's a strong possibility they will turn on their creators.
And at that point, you might as well use OpenRouter's PKCE and give users the option to use other models..
These kinds of business decisions show how these $200.00 subscriptions for their slot/infinite jest machines basically light that $200.00 on fire, and in general how unsustainable these business models are.
Can't wait for it all to fail, they'll eventually try to get as many people to pay per token as possible, while somehow getting people to use their verbose antigentic tools that are able to inflate revenue through inefficient context/ouput shenanigans.
I think the subscription pricing exists because it’s a far more palatable way to bill people for day to day personal use.
I used Claude back when API per token pricing was the only option and it was bad for all the usual reasons pay-per-use sucks compared to flat billing: you’re constantly thinking about cost. Like trying to watch a Netflix video with a ticker in the corner counting up the cents you owe them.
I don’t understand your claim that they want people paying per token - the subscription is the opposite of that, and it also has upsides for them as a business since most people don’t saturate the usage limits, and the business gets to stuff a bunch of value-adds on a bundle offering which is generally a more lucrative and enticing consumer pricing model.
The bundle only works if it’s +EV for them. A lot of analyses (though not all - it’s complicated) say that the $200/mo bundle (and certainly the $20/mo bundle) costs more than that for most users, and the bundle is currently a loss leader. If so, then eventually prices will need to go up, and API per usage pricing will seem much more attractive.
9 replies →
The cost difference is pretty staggering for the same usage. Being on the sub hacks your reward system to push you to be productive, legitimately hitting limits feels like a win, and you start looking for ways to max your utilization %. A lot of people get quite obsessive about it. The sub is 100% the innovation that makes Claude Code "work."
If the pay-per-use cost predictable enough, it’s less of an issue. That’s how electricity works and it’s fine.
The issue with Claude Code is it’s not at all obvious how any given task or query translates to cost. I was finding some days I spent very little and other days cost a fortune despite what seemed to me to be similar levels of usage.
People 100% want subscriptions in this space.
The alternative is AWS where you need to be a billing expert to keep costs locked at $20/month.
It’s been obvious from the start that the $200 point is the free tier
You are talking about Anthropic and indeed compared to OpenAI or GitHub Copilot they have seemed to be the ones with what I would personally describe as a more restrictive approach.
On the other hand OpenAI and GitHub Copilot have, as far as I know, explicitly allowed their users to connect to at least some third party tools and use their quotas from there, notably to OpenCode.
What is unclear to me is whether they are considering also allowing commercial apps to do that. For instance if I publish a subscription based app and my users pay for the app itself rather than for LLM inference, would that be allowed?
Same question here. A while ago I read rumors OpenAI might build a "Login with OpenAI" (comparable to login with Apple, Facebook, Google) so people can also use their existing sub in commercial apps. Hope it's true.
Then why does the SDK support subscription usage? Can I at least use my subscription for my own use of the SDK?
What if you wrap the service using their Agent SDK?
That should be fine, because it's still using their tooling. And this seems like the better way to go. I have a couple of tools that work like this. I think the issue is mostly 3rd party harnesses that seek to do the same as Claude Code. And it seems reasonable that Anthropic decides how you can use the subscription, because it's heavily subsidized. Get a Claude $200 sub and max out the usage limits, then compare that usage to the cost of using their API. The difference is significant, which is why people are getting multiple $200 subs rather than paying for API usage (and I have seen reports where they are cracking down on this as well.)
It literally says in the linked page it's not fine.
2 replies →
Quick question but what if I use claude code itself for the purpose?
https://news.ycombinator.com/item?id=46912682)
This can make Opencode work with Claude code and the added benefit of this is that Opencode has a Typescript SDK to automate and the back of this is still running claude code so technically should work even with the new TOS?
So in the case of the OP. Maybe Opencode TS SDK <-> claude code (using this tool or any other like this) <-> It uses the oauth sign in option of Claude code users?
Also, zed can use the ACP protocol itself as well to make claude code work iirc. So is using zed with CC still allowed?
> I don't see how they can get more clear about this, considering they have repeatedly answered it the exact same way.
This is confusing quite frankly, there's also the claude agent sdk thing which firloop and others talked about too. Some say its allowed or not. Its all confusing quite frankly.