alt Hacker NewsWe are in a bubble, but you are looking at this in the wrong way. OpenRouter basically creates lock-in through Stripe's distribution and family of products; it is much stronger within Stripe than alone. I agree valuations are absurd, but it is what it is. But if we have to go through a bubble for a16z to crash and burn, I am all for it.
So customers use OpenRouter to avoid lock-in to specific model providers, and in doing so they lock-in into openrouter's aggregation API?
Lock-in to what exactly? A string(string) function without any further restrictions? Note that aggregator users will not use more specific parameter features (because those vary by vendor), or they escape the aggregator and lock-in directly string(string, vendorOptions={"openAI.logprobs":true})
Selling vendor lock-in to vendor lock-in avoidant customers sounds like a losing proposition, like trying to beat competition on price and undercutting, which is a thing openrouter does too btw, the main reason people use these products is to get cheaper prices. I don't think 2$/M tokens is expensive, and I don't think those that try to cut costs are going to win, whether devs cutting token costs, or small business owners with 5 employees who look at AI as a way to fire 2 of them. I get that the other end of the spectrum is overspending and tokenmaxxing, but the conclusion is that extremes are bad? Nothing new here.