Comment by bilekas
6 days ago
It might be some confirmation bias here on my part but it feels as if companies are becoming more and more hostile to their API users. Recently Spotify basically nuked their API with zero urgency to fix it, redit has a whole convoluted npm package your obliged to use to create a bot, Facebook requires you to provide registered company and tax details even for development with some permissions. Am I just old man screaming at cloud about APIs used to being actually useful and intuitive?
They put no limits on the API usage, as long as you pay.
Here, they put limits on the "under-cover" use of the subscription. If they can provide a relatively cheap subscription against the direct API use, this is because they can control the stuff end-to-end, the application running on your system (Claude Code, Claude Desktop) and their systems.
As you subscribe to these plans, this is the "contract", you can use only through their tools. If you want full freedom, use the API, with a per token pricing.
For me, this is fair.
> If they can provide a relatively cheap subscription against the direct API use
Except they can't. Their costs are not magically lower when you use claude code vs when you use a third-party client.
> For me, this is fair.
This is, plain and simple, a tie-in sale of claude code. I am particularly amused by people accepting it as "fair" because in Brazil this is an illegal practice.
> This is, plain and simple, a tie-in sale of claude code. I am particularly amused by people accepting it as "fair" because in Brazil this is an illegal practice
I am very curious what is particularly illegal about this. On the sales page nowhere do they actually talk about the API https://claude.com/pricing
Now we all know obviously the API is being used because that is how things work, but you are not actually paying a subscription for the API. You are paying for access to Claude Code.
Is it also illegal that if you pay for Playstation Plus that you can't play those games on an Xbox?
Is it illegal that you can't use third party netflix apps?
I really don't want to defend and AI company here but this is perfectly normal. In no other situation would we expect access to the API, the only reason this is considered different is because they also have a different service that gives access to the API. But that is irrelevant.
42 replies →
I've heard they actually cache the full Claude Code system prompt on their servers and this saves them a lot of money. Maybe they cache the MCP tools you use and other things. If another harness like Opencode changes that prompt or adds significantly to it, that could increase costs for them.
What I don't understand is why start this game of cat and mouse? Just look at Youtube and YT-DLP. YT-DLP, and the dozens of apps that use it, basically use Youtube's unofficial web API and it still works even after Youtube constantly patches their end. Though now, YT-DLP has to use a makeshift JS interpreter and maybe even spawn Chromium down the line.
4 replies →
> Their costs are not magically lower when you use claude code vs when you use a third-party client.
If subsidizing that offering is a good hook to get higher paying API users on board, then some of that cost is a customer aquisition cost, whereas the cost to them of providing the API doesn't have the same proportion that they can justify as a customer acquisition cost.
4 replies →
Unless it's illegal in more places, I think they won't care. In my experience, the percentage of free riders in Brazil is higher (due to circumstances, better said).
While the cost may not be lower the price certainly can be if they are operating like any normal company and adding margin.
But they could charge the third-party client for access to the API.
> Except they can't. Their costs are not magically lower when you use claude code vs when you use a third-party client.
I don't have a dog in this fight but is this actually true? If you're using Claude Code they can know that whatever client-side model selection they put into it is active. So if they can get away with routing 80% of the requests to Haiku and only route to Opus for the requests that really need it, that does give them a cost model where they can rely on lower costs than if a third-party client just routes to Opus for everything. Even if they aren't doing that sort of thing now, it would be understandable if they wanted to.
7 replies →
I think what most people don't realize is running an agent 24/7 fully automated is burning a huge hole in their profitability. Who even knows how big it is. It could be getting it on the 8/9 figures a day for all we know.
There's this pervasive idea left over from the pre-llm days that compute is free. You want to rent your own H200x8 to run your Claude model, that's literally going to cost $24/hour. People are just not thinking like that. I have my home PC, it does this stuff I can run it 24/7 for free.
there are usage limits preventing you from running it 24/7 on all subscriptions tiers
1 reply →
I understand you mean for free in the sense that you don't pay a third party to use it, however let's no forget that you still use the power grid and that's not free. Also worth to note that energy prices have increased worldwide.
3 replies →
Sure it's $24/hour, but it'll crank through tens of thousands of tokens per second --- those beefy GPUs are meant for large amounts of parallel workflow. You'll never _get_ that many tokens for a single request. That's why the mathematics work when you get dozens or hundreds of people using it.
No. The sauce is in KV caching: when to evict, when to keep, how to pre-empt an active agent loop vs someone who are showing signs of inactivity at their pc, etc.
Coder doing the coding should use subscription, and now they ban the choice of your preferred ide for agentc coding. API is for automation not coding. I'm going to cancel their subscription today, I already use codex with opencode.
This is honestly the key difference here. I’m morally okay with using Claude Max Whatever with something like OpenCode because it’s literally the same thing from the usage pattern perspective. Plugging Nanoclaw into it is a whole another thing.
7 replies →
I don't see how it's fair. If I'm paying for usage, and I'm using it, why should Anthropic have a say on which client I use?
I pay them $100 a month and now for some reason I can't use OpenCode? Fuck that.
You aren't paying for usage, you are paying for the product that the subscription is offered to. If you are paying for usage, well, that's their billed by token-usage API plan, which they are quite happy for you to use with any client you want.
9 replies →
> If I'm paying for usage
You are not paying for usage. You are paying for usage via their application.
If their business plan is based on how quickly a human can enter requests and react to the results, and Claude Code is optimized for that, why should you be allowed to use an alternative client that e.g. always tries to saturate the token limits?
7 replies →
Stop giving money to the company that doesn't give you what you want.
4 replies →
You're touching on the eternal App Store debate. "It's my phone, I should be able to install whatever I want on it!" Which is true, but also hasn't been true since the mid-90s (early 2000s at the latest).
1 reply →
Read the ToS, you are paying to use their products. If you want to use other products that integrate with the Anthropic LLMs they offer a product which is the API. You can use Opencode by connecting your API and being charged per token.
Doesn't that make sense? If you use it more you get charged more, if you use it less you get charged less.
3 replies →
Now just imagine the rug-pull if you ever get really dependent on the product.
Their subscriptions aren't cheap, and it has nothing really to do with them controlling the system.
It's just price differentiation - they know consumers are price sensitive, and that companies wanting to use their APIs to build products so they can slap AI on their portfolio and get access to AI-related investor money can be milked. On the consumer-facing front, they live off branding and if you're not using claude code, you might not associate the tool with Anthropic, which means losing publicity that drives API sales.
It would be less of an issue if Claude-Code was actually the best coding client, and would actually somehow reduce the amount of tokens used. But it's not. I get more things done with less tokens via OpenCode. And in the end, I hit 100% usage at the end of the week anyway.
The problem is incentives. The organization selling the per-token model doesn't have the incentive, at scale to have you reduce token consumption. Other technologies do, hence adding value.
It doesn't really make sense to me because the subscriptions have limits too.
But I agree they can impose whatever user hostile restrictions they want. They are not a monopoly. They compete in a very competitive market. So if they decide to raise prices in whatever shape or form then that's fine.
Arbitrary restrictions do play a role for my own purchasing decisions though. Flexibility is worth something.
I'm with the parent comment. It was inevitable Netflix would end password-sharing. It was inevitable you'd have to pick between freeform usage-based billing and a constrained subscription experience. Using the chatbot subscription as an API was a weird loophole. I don't feel betrayed.
They tier it. So you are limited until you pay more. So you can't just right away get the access you need.
[dead]
I don't and would never pay for an LLM, but presumably they also want for force ads down your throat eventually, yea? Hard to do if you're just selling API access.
But the idea of an API is more to encourage creativity and other people/companies building products and services on or around your systems. This used to be seen as a positive as it would mean you were an important cog in other peoples products and so more users, exposure, brand awareness etc.
2 replies →
Compared to the heavily subsidized subscriptions, I don't think API is sold at loss.
Also why would you create a throwaway for this question? Are you trying to rage bait?
2 replies →
1:29 until you're able to push to the `main` branch.
Please enjoy these messages from our sponsors.
Every garden eventually becomes a walled garden once enough people are inside.
#earthisamoat
Enshittification
[flagged]
What a weird metaphor for a company which most likely wants nothing more than growing markets.
2 replies →
Spotify are probably reacting to https://annas-archive.li/blog/backing-up-spotify.html where basically the whole archive was downloaded
that was later.
It was known publicly later.
Can you sell ads via api? If answer is no then this “feature” would be at the bottom of the list
They can sell API access via transparent pricing.
Instead, many, many websites (especially in the music industry) have some sort of funky API that you can only get access to if you have enough online clout. Very few are transparent about what "enough clout" even means or how much it'd cost you, and there's like an entire industry of third-party API resellers that cost like 10x more than if you went straight to the source. But you can't, because you first have to fulfill some arbitrary criteria that you can't even know about ahead of time.
It's all very frustrating to deal with.
Plus, use of the API is a way to avoid ads. So double-strike against good/available APIs.
Of course they can [1].
Though, in this case, you get free API access to the model.
[1]: https://x.com/badlogicgames/status/2017063228094709771
There is a world where approaches like HTTP 402 are implemented to monetize API usage.
Please get this token signed by our ad partner to enable your next ten requests.
What kind of ads they sell in terminal Claude code? Are you bor?
See [1] for a solution.
[1] https://i.programmerhumor.io/2025/03/778c56a79115a582edb9949...
I think that these companies are understanding that as the barrier to entry to build a frontend gets lower and lower, APIs will become the real moat. If you move away from their UI they will lose ad revenue, viewer stats, in short the ability to optimize how to harness your full attention. It would be great to have some stats on hand and see if and how much active API user has increased decreased in the last two years, as I would not be surprised if it had increased at a much faster pace than in the past.
> the barrier to entry to build a frontend gets lower
My impression is the opposite: frontend/UI/UX is where the moat is growing because that's where users will (1) consume ads (2) orchestrate their agents.
I agree with you - we are saying the same thing, by restricting their API or making less developer friendly, they want you to be captive in their UI. This might not be true for Anthropic or OpenAI - another child commenter made a comment about ads in CLI, I would not be surprised if in a while we will have product placements in LLM responses exactly as we have it in movies - not a plain ad but just a slightly less subliminal suggestion.
1 reply →
It’s objectively easier to build a frontend now and therefore that moat is disappearing. What you can argue is the moat is in incumbent advantage at the UI layer, not the UI itself.
What ad revenue? In their terminal cli?
I don't it's particularly hard to figure it out: APIs have been particularly at risk of being exploited for negative purposes due the explosion of AI powered bots
This trend well predates widespread use of chatbots.
It's just the continued slow death of the open internet
Google now wants $30,000 a month for customsearch (minimum charge), up from 1c per search or thereabouts in January 2026...
I’m predicting that there would be a new movement to make everything an MCP. It’s now easier to consume an api by non technical people.
It's because AI is being trained on all of these APIs and the platforms are at risk of losing what makes them valuable (their data). So they have to take the API down or charge enough that it wouldn't be worth it for an AI.
APIs leak profit and control vs their counterpart SDK/platforms. Service providers use them to bootstrap traffic/brand, but will always do everything they can to reduce their usage or sunset them entirely if possible.
What is given can be taken away. Despite the extra difficult this is why unofficial methods (e.g. scraping) are often superior. Soon we'll see more fully independent data scraping done by cameras and microphones.
There is no moat except market saturation and gate keeping for most platforms.
You're correct in your observations. In the age of agents, the walls are going up. APIs are no longer a value-add; they're a liability. MCP and the equivalent will be the norm interface. IMO.
This is sort of true!
Spotify in particular is just patently the very worst. They released an amazing and delightful app sdk, allowing for making really neat apps in the desktop app in 2011. Then cancelled it by 2014. It feels like their entire ecosystem has only ever gone downhill. Their car device was cancelled nearly immediately. Every API just gets worse and worse. Remarkable to see a company have only ever such a downward slide. The Spotify Graveyard is, imo, a place of singnificantly less honor than the Google Graveyard. https://web.archive.org/web/20141104154131/https://gigaom.co...
But also, I feel like this broad repulsive trend is such an untenable position now that AI is here. Trying to make your app an isolated disconnected service is a suicide pact. Some companies will figure out how to defend their moat, but generally people are going to prefer apps that allow them to use the app as they want, increasingly, over time. And they are not going to be stopped even if you do try to control terms!
Were I a smart engaged company, I'd be trying to build WebMCP access as soon as possible. Adoption will be slow, this isn't happening fast, but people who can mix human + agent activity on your site are going to be delighted by the experience, and that you will spread!
WebMCP is better IMHO than conventional APIs because it layers into the experience you are already having. It's not a separate channel; it can build and use the session state of your browsing to do the things. That's a huge boon for users.
Facebook doing that is actually good, to protect consumers from data abuse after incidents like cambridge analytica. They are holding businesses who touches your personal data responsible.
> Facebook doing that is actually good, to protect consumers from data abuse after incidents like cambridge analytica.
There is nothing here stopping cambridge analytica from doing this again, they will provide whatever details needed. But a small pre launch personal project work that might use a facebook publishing application can't be developed or tested without first going through all the bureaucracy.
Nevermind the non profit 'free' application you might want to create on the FB platform, lets say a share chrome extension "Post to my FB", for personal use, you can't do this because you can't create an application without a company and IVA/TAX documents. It's hostile imo.
Before, you could create an app, link your ToS, privacy policy etc, verify your domain via email, and then if users wanted to use your application they would agree, this is how a lot of companies still do it. I'm actually not sure why FB do this specifically.
Facebook knew very early and very well about the data harvesting that was going on at Cambridge Analytica through their APIs. They acted so incredibly slowly and not-harsh that it's IMO hard to believe that they did not implicitly support it.
> to protect consumers
We are talking about Meta. They have never, and will never, protect customers. All they protect is their wealth and their political power.
Is it? I’ve never touched Facebook api, but it sounds ridiculous that you need to provide tax details for DEVELOPMENT. Can’t they implement some kind of a sandbox with dummy data?
You can mock their API all you want for development and there are many pre-built options for that, but it you want to touch their systems, they're sending a very clear signal. You must be a corporate with an RBO. Seems prudent to me.
WhatsApp takes bot spam very very seriously, and as a result, there is zero bot spam.
Before you can sign up to build a WhatsApp bot, you need to jump through a million hoops, and after that, every automated message template must be vetted by Meta before it can be sent out, apple style.
I'm glad of this, because unlike SMS and other messaging platforms, WhatsApp is spam free and a pleasure to use.
2 replies →
They just want people to use facebook. If you can see facebook content without being signed in they have a harder time tracking you and showing you ads.
Given the Cambridge Analytica scandal, I don’t take too much issue to FB making their APIs a little tougher to use
„Open Access APIs are like a subway. You use them to capture a market and then you get out.“
— Erdogan, probably.
Not sure how relevant this comment is
Everyone has heard the word "enshittification" at this point and this falls in line. But if you haven't read the book [0] it's a great deep dive into the topical area.
But the real issue is that these companies, once they have any market leverage, do things in their best interest to protect the little bit of moat they've acquired.
[0] https://www.mcdbooks.com/books/enshittification
"Are becoming", you sweet summer child.
It all started with Facebook closing pretty much everything and making FB Messenger a custom protocol instead of XMPP.
And whatever API access is still available is so shit and badly managed that even a household name billion dollar gaming company couldn't get a fast-lane for approval to use specific API endpoints.
The final straw was Twitter effectively closing up their API "to protect from bots", which in fact did NOT protect anyone from bots. All it did was prevent legitimate entertaining and silly bots from acting on the platform, the actual state-controlled trolls just bought the blue checkmark and continued as-is.
But this ban is precisely on circumventing the API.
APIs are the best when they let you move data out and build cool stuff on top. A lot of big platforms do not really want that anymore. They want the data to stay inside their silo so access gets slower harder and more locked down. So you are not just yelling at the cloud this feels pretty intentional.
That is not new, just new with APIs.
The usual cycle with startups is to:
- Start being very open, as this brings people developing over the platforms and generates growth
- As long as they are growing, VC money will come to pay for everything. This is the scale up phase
- Then comes the VC exit, IPO or whatever
- Now the new owners don't want user growth, they want margin growth. This is the company phase
- Companies then have monetize their users (why not ads?), close up free, or high-maintenance stuff that do not bring margin
- and report that sweet $$$ growth quarter after quarter
...until a new startup comes in and starts the cycle over again, destroying all the value the old company had.
A mix of Enshittification and Innovators Dilemma theories
You're not wrong. Reddit & Elon started it and everyone laughed at them and made a stink. But my guess is the "last dying gasp of the freeloader" /s wasn't enough to dissuade other companies from jumping on the bandwagon, cause fiduciary responsibility to shareholders reigns supreme at the end of the day.