←back to thread

Build and Host AI-Powered Apps with Claude – No Deployment Needed

(www.anthropic.com)
325 points davidbarker | 1 comments | 25 Jun 25 17:14 UTC | HN request time: 0.283s | source
Show context
jonplackett ◴[25 Jun 25 19:38 UTC] 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 #
nsoonhui ◴[26 Jun 25 06:55 UTC] 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 #
Pmop ◴[26 Jun 25 07:16 UTC] 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 #
wwdx ◴[26 Jun 25 09:23 UTC] No.44385630[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 #
1. cranium ◴[26 Jun 25 09:49 UTC] No.44385766[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,...).