Most active commenters
  • jonplackett(4)
  • mbm(3)
  • pzo(3)

←back to thread

325 points davidbarker | 30 comments | | HN request time: 7.038s | source | bottom
1. jonplackett ◴[] No.44381121[source]
I used to love to make silly websites or apps with new technologies. Been doing it since flash. I have a pretty decent hit rate! It’s not unusually to get half a million or so people try one of them.

But with AI that model is just totally broken because the running cost is so high.

If I have half a million people come play my silly AI game that I have no wish to monetise - I am gonna be POOR very fast.

Log in with [insert ai vendor here] is something I’ve been hoping would happen for a while.

replies(6): >>44381339 #>>44381554 #>>44381710 #>>44381790 #>>44384881 #>>44388950 #
2. ◴[] No.44381339[source]
3. mbm ◴[] No.44381554[source]
Agreed, it's an interesting model. I wonder what the approval ui looks like for the app end-user? Is it super clear to them that they're financially responsible for their usage?
replies(1): >>44381603 #
4. jonplackett ◴[] No.44381603[source]
Yeah I wonder how that actually works - because I would guess people are logging in with their consumer login not an api login, so they’re not really even in the mindset of limits and cost per token.
replies(1): >>44381774 #
5. gavmor ◴[] No.44381710[source]
"Log in With Google" to use Drive storage has long been a thing. Maybe proxying Gemini usage isn't too far off.
replies(1): >>44382916 #
6. mbm ◴[] No.44381774{3}[source]
Precisely. You click on a claude link, and suddenly it's, "You are now financially responsible for your actions from here on..." I'm sure they've spent a lot of time thinking through the ui/ux of this.
replies(1): >>44382955 #
7. jerpint ◴[] No.44381790[source]
This is seriously lacking but I think things like jailbreaks and malicious prompts make it a bit too brittle for now
replies(1): >>44382209 #
8. jonplackett ◴[] No.44382209[source]
The thing is though, it doesn’t need to have access to your personal info in the context, so it cant leak anything. And they are obviously used to people talking all sorts of jailbreak shit to their chatbot - so it isn’t really much worse than that.

Also I reckon the cost of running a text chatbot is basically peanuts now (that is, for a giant tech company with piles of hard cash to burn to keep the server farm warm)

9. dcl ◴[] No.44382916[source]
"Bring your own AI" or "Provide your AI API access key" will probably be coming to a lot of services/apps that we want 'our' AI's to interact with.

I can see this also bringing strongly tiered AI's, there will be commodity/free AI's a and expensive ones for rich people/power users.

replies(3): >>44383224 #>>44383308 #>>44383907 #
10. ameliaquining ◴[] No.44382955{4}[source]
Users of Claude-hosted apps can't thereby incur financial liability, because it counts against the usage limit of their consumer Claude plan, which either is free or has a fixed monthly subscription price. The worst that can happen is that they run out of quota and can't use Claude anymore until it resets, which happens every day on free plans and every five hours on paid ones. In no case is usage attributed to an API key with metered pricing.
replies(1): >>44383302 #
11. gavmor ◴[] No.44383224{3}[source]
I just hope I live to see the day personal agents are empowered to make ad hoc use of paid services on our behalf—via eg AITP (Agent Interaction & Transaction Protocol), which is specifically designed to enable autonomous, secure communication, negotiation, and value exchange between agents across trust boundaries. AITP includes explicit capabilities for "Payments" (AITP-01) and "Data Request" (AITP-03), allowing structured sharing of sensitive information like addresses and passwords that can be programmatically verified and executed.

Similarly, the Coral Protocol aims to be an open and decentralized infrastructure for "The Internet of Agents," with "built-in economic transactions" at its core. This means agents can be compensated for their contributions via on-chain micropayments

Oh, damn, no, that sounds like an expense-tracking nightmare. Budgeting becomes the principal executive input.

replies(2): >>44384696 #>>44387981 #
12. mbm ◴[] No.44383302{5}[source]
Ah true. So the push becomes even stronger for people to upgrade to the max plans, when several of the "apps" they're using are consuming their allocated Claude tokens. Brilliant.
13. kgdiem ◴[] No.44383308{3}[source]
Snowflake does revenue sharing, it’s possible that AI providers can start doing that too.
replies(1): >>44389122 #
14. cube00 ◴[] No.44383907{3}[source]
> "Provide your AI API access key" will probably be coming to a lot of services/apps that we want 'our' AI's to interact with.

Considering provide your own API key is banned by a number of larger players (Reddit, Google Maps) to stop large numbers of users cashing in on the free/cheap low usage tiers I'd expect AI vendors would enforce the same rules soon once all this free VC hype funding dries up.

replies(1): >>44389111 #
15. nsriv ◴[] No.44384696{4}[source]
Last line of your comment is what I was thinking the entire time. Another layer of abstraction between our minds and our wallets.
16. nsoonhui ◴[] No.44384881[source]
>> If I have half a million people come play my silly AI game that I have no wish to monetise - I am gonna be POOR very fast.

But the article says:

  When someone uses your Claude-powered app:

  They authenticate with their existing Claude account
  Their API usage counts against their subscription, not yours
  You pay nothing for their usage
  No one needs to manage API keys
So how would that impact you?
replies(4): >>44384995 #>>44385000 #>>44385210 #>>44389985 #
17. Pmop ◴[] No.44384995[source]
Yep. Meanwhile I’m trying to figure out how can I make something that people would want to pay for, and how can I charge them, if they’re going to interact directly with Claude and burn their own quota.
replies(1): >>44385630 #
18. ◴[] No.44385000[source]
19. archerx ◴[] No.44385210[source]
That's still no good. The only real way it could work is by having models running locally with WASM.
20. wwdx ◴[] No.44385630{3}[source]
anthro needs to let the creator charge % on top of their usage quota or give points/money to the creator to fix up the incentives here
replies(3): >>44385766 #>>44391052 #>>44396072 #
21. cranium ◴[] No.44385766{4}[source]
That's a really good idea! That would handle micropayments that nobody would even bother with (to pay, to process, to receive, ...).

Could even have users select the payment %age or have it set by the contract tier between the app creator and the user (10% for simple user, 20% for pro access with other features, 40% enterprise,...).

22. BoiledCabbage ◴[] No.44387981{4}[source]
JFC, these crypto people never stop! No matter how many times their tech has shown itself it be just about useless other than for illegal activities or for scamming people, they keep pushing it in every new tech space that exists.

I swear 100 years from now someone will be inventing faster then light travel, and there will be some tech scammers posting on HN on "how much better it would be on chain". Or how "the engine could be better if it used a decentralized crypto protocol."

The allure of being in the ground floor of a new scam just must be that great.

23. abraham ◴[] No.44388950[source]
On-device models seems like a good approach to this. Especially if it's silly projects they probably don't need the latest and greatest expensive models.

Firebase recently launch some experimental on-device APIs. https://firebase.blog/posts/2025/06/hybrid-inference-firebas...

24. pzo ◴[] No.44389111{4}[source]
any details on this? how they can even detect it or ban it?
replies(1): >>44394657 #
25. pzo ◴[] No.44389122{4}[source]
do you have a link where I can read more about it?
26. jonplackett ◴[] No.44389985[source]
That’s exactly my point, like now it wouldn’t, previously it would.
27. monadoid ◴[] No.44391052{4}[source]
Yes I agree strongly, if I could just make a small percentage for my mildly interesting LLM wrapper it would be perfect! @anthropic please implement this
28. cube00 ◴[] No.44394657{5}[source]
It's in their TOS. Trivial to ban you when they see thousands of different keys coming from a single IP.
replies(1): >>44429978 #
29. owebmaster ◴[] No.44396072{4}[source]
That's what I've been preaching, too. The provider that does it, will win the game.
30. pzo ◴[] No.44429978{6}[source]
not sure what CORS rule they have but in edge apps most likely your users will run AI API directly from their devices so not like their key will be used more than on few edge devices they have.