Replies: 1 comment
|
It even says it does for openai, but I don't think so. I don't see
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
Why does every change in models or pricing need a new PR and new release? E.g. #1755 and #1756
It would be nice if this was just a simple json file for each provider with model definitions. It could live in a separate repo that can be updated much more regularly and hosted on github pages and/or some other CDN like CloudFlare. Then cache it locally for an hour or even 24 hours with a simple button to download the latest definitions.
The model definitions are basically json already.
Then you can have another repo with scripts that automatically hit the respective providers' APIs for updates, such as
https://api.openai.com/v1/modelsorhttps://openrouter.ai/api/v1/models, after which it will push changes to the repo with just the json model definitions. Or do it manually, which would still be much easier than currently, where each change requires a new PR.You can even do schema versioning if backwards compatibility is a concern, so a schema change wouldn't break current/older versions.
All reactions