upvote
You don't pay for capacity, you pay for an interface. Paying for capacity is what API keys are for.

Similarly, on a home internet connection you might pay for a given size of pipe, but most residential ISPs don't allow running publicly accessible servers on your connection because you'll typically use way more of the bandwidth.

reply
If that same internet provider has caps on how much bandwidth I can use every 5 hours and total on a weekly basis, then yes, I pay for capacity.

That argument would have been valid when the 5 hours blocks were unlimited in the beginning.

reply
My home ISP, as most are now, have "unlimited downloads". There's no limit on usage by numbers, because consumers don't like that. Instead there's limit on usage by style. I can't run a public server on it, and I don't get a business SLA. For home usage that's ideal, I don't need those things but I don't want to worry about limits.

These plans vs API keys issues are exactly the same concept.

reply
This is probably one of the worst analogies you could have brought up in this context.

The business model of an ISP involves fixed capital investments into infrastructure with constant opex and very little variable costs.

The marginal cost of sending a gigabyte is basically zero. The limited resource here is bandwidth and ISPs split their tiers based on bandwidth.

The problem is that some users may consume the local bandwidth that is shared with other users. More bandwidth requires more investment into infrastructure. This means that bandwidth in itself doesn't produce costs for the ISP either, it is the maximum bandwidth capacity that costs money.

Hence, oversubscription is a viable business as long as neighbors aren't impacted by power users.

This doesn't apply to LLMs. Token economics has the same economics as steel. There is high capex to get started, but the real killer is the variable cost per unit of steel.

You can't sell steel on a oversubscribed subscription model. It's nonsensical.

If the subscription is more expensive than buying what you need, nobody is going to pay for the subscription unless they consume all of it.

Hence the subscription must contain a subsidy to make it competitive.

However, the people who consume the full subscription are still there and each token they request adds up on your electricity bill.

Ergo, the subscription must be more expensive than the API, but with a smart billing limit that removes the cognitive burden of using your service with pay as you go billing.

reply
[flagged]
reply
A Claude Code subscription is a subscription to … Claude Code … which is an interface.

The API keys are how you use models directly.

reply
I’m not sure why people expect Anthropic to subsidize tokens through Open Claw when it’s specifically forbidden in the ToS.
reply
^ This. I get that We Are On The Internet And People Will Be Wrong Sometimes -- but I'm really confused by the amount of people insisting that a subscription is just a slosh bucket of token capacity to be used however they feel like using it; are these people who genuinely misunderstand how subscriptions work or what Anthropic's terms were, and genuinely weren't aware that 3rd-party harnesses violate them? The vibe I get is more "how dare you constrain me from doing whatever I want", angry rebellious teenager vibe, willful oversimplifications of the situation... it doesn't feel particularly honest or reality-seeking.
reply
Didn’t know I’m paying for capacity. Learnt something new today!
reply
Meh this argument does not hold up. If you don’t like it pay for the API. We all know these services are priced for human use, as in your not using it 24/7.
reply
Except no, you aren't paying the full capacity of using all of your limits every time. The subscription cost is less than it would take to actually pay for the capacity of the limits. That is how these sorts of subscriptions work.

You can pay for the capacity, using the per token price.

reply