Ask HN: Is token-based pricing making AI harder to use in production?
3 points| Barathkanna | 1 month ago
I’ve noticed a recurring theme in many threads here: AI is powerful, but once you move past demos, token based pricing becomes expensive and hard to reason about.
We ran into this problem ourselves while building AI powered systems. Predicting costs, budgeting usage, and experimenting safely all got harder as workloads grew. So we built a small AI API platform for inference, aimed at early developers and small teams who want to integrate AI without constantly calculating token usage. The focus is on lower and more predictable costs rather than chasing the newest model.
This is still early, and I’m mainly posting to learn from others here. For people running AI in production, what’s been the hardest part to manage so far? Cost, predictability, performance, or something else?
I’d really appreciate any insights or experiences.
elmascato|1 month ago
I'm seeing a strong parallel in SaaS regarding Purchasing Power Parity (PPP). We often assume a user in India or Brazil doesn't convert because they "can't afford" $49, but the friction is often psychological. Even for high earners in those regions, paying a double-digit USD subscription feels "wrong" or predatory relative to local goods.
Just as you are abstracting away the token math to lower the barrier to entry, we need to abstract away the currency inequality. I've been working on a client-side widget to handle this (tierwise.dev) and noticed that simply aligning the price with the user's local context making it "feel" fair spikes conversion rates significantly.
Whether it's flattening token variance or localizing purchasing power, the goal is the same: stop the user from doing math and let them focus on the product value.
iamrobertismo|1 month ago
Barathkanna|1 month ago
I agree that token economics are basically a commodity today. The problem we’re trying to address isn’t beating the market on raw token prices, but removing the mental and financial overhead of having to model usage, estimate burn, and worry about runaway costs while experimenting or shipping early features. In that sense it’s absolutely an engineering and finance problem combined, and we’re intentionally tackling it at the pricing and API layer rather than pretending the underlying models are unique.