Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

i have seen this so many times...

i'm thinking it's time we replaced api keys.

some type of real time crypto payment maybe?



Prepaid only is a fantastic idea, especially for dumb-ass startups. Limiting your liability to $100 or so sound like a big-ass W.


Yes, pre-paid would be fine and it's a well-understood pattern.

No need to retire API keys.


Nobody is thinking about the stock owners, I see


Implementing this in any meaningful manner quickly begins to look like every read becoming a globally synchronised write. Of course it doesn't have to be perfect, but even approximating perfection doesn't look much different. Also, can you imagine the kind of downtimes and complaints that would inevitably originate from a fully synchronous billing architecture?


> Of course it doesn't have to be perfect, but even approximating perfection doesn't look much different.

It's pretty easy to get right, if the provider allows you to go (slightly) negative before cutting you off.

> Also, can you imagine the kind of downtimes and complaints that would inevitably originate from a fully synchronous billing architecture?

Doesn't need to fully synchronous.


Open ai has this


Prepaid only is a fantastic idea, until your site goes (desirably) viral and then gets shut off right as traffic is picking up, or you grow steadily and forget to increase your deposit amount and suddenly production is down. Billing alerts are a much better solution IMHO.


the planning-your-day-around-the-window thing is real and underrated as a cost. the limits don't just hit you at the moment you hit them, they change how you work for the entire day around them. we're building something called Traeco that tells you what's actually eating your limit per step so you can at least see what's burning fast vs what's fine — happy to share early access if you want to try it.

No you big dummy, that is especially when you want to limit your liability, lol.

Because these days it will be all worthless bot traffic.


Prepaid/paid limits with shutoff is appropriate for this though.

If you have per key limits, this is not possible, and even in a wild situation you should b able to expect that your firebase key will not use 50k.


Let me choose. This common point seems more like a rationalization for the default behavior of hyperscalers. AWS isn't avoiding prepaid due to concern about my site's virality, just that prepaid = less money.


You can also have both, a cap and one or more billing alert levels below it. Some providers do this (e.g. IIRC Backblaze B2).


Yes in reality, and ideally, you can have both, but GP specifically said "Prepaid only" implying you can't have both (which is what I replied to)


Well, they should also have pre-paid only. Offer a few different options.


Oh please no. And the "alternatives" to API keys aren't going to help much either, they'll just add friction to getting started (as reference: see the pain involved in writing a script that hits gmail or calendar API)




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: