3 ms·
neat idea. random tiny piece of site feedback: make the hero backgrounds dark so that the text is legible as the image loads in. more constructively, this is t
by rgbrgb 2y ago
neat idea. random tiny piece of site feedback: make the hero backgrounds dark so that the text is legible as the image loads in.
more constructively, this is the kind of code ai is great at writing in my codebase and once it’s there locally as a library, it’s free. it’s not clear to me why I’d want it behind an api instead, at least as a solo-ish dev. I’d recommend looking at the similar openrouter that seems to have some traction and think about why users are using them. You might also think about deeper agent or eval stuff you could add that are beyond the scope of the little backend switching lib I could have Claude write. Anyway, good luck and thanks for sharing!
- johnmcelhone 2y agoThanks for the feedback! Will work on some updates for the hero backgrounds. On your point about local code vs. API: - We handle all the authentication, rate limiting, and API differences between providers, which becomes complex when working with multiple models. Our platform allows smart switching between different models depending on the message context. - Our switching is optimized for performance. We provide detailed usage analytics and cost management across models so you can optimize which models to use where. This allows you to see what costs your users may be incurring / misbehaving. We're building features that go beyond what's easily replicable locally, including some of the agent and evaluation capabilities you mentioned (rolling out over the next two weeks). OpenRouter is definitely doing great things in this space. We're taking a slightly different approach by focusing on bringing customization within the dashboard to allow for on-the-fly updates without pushing new code edits. Appreciate the feedback and hopefully you get a chance to try out the tool!