anomalyco / anomalyco/models.dev
Outdated data for openrouter provider
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.9k
- Forks
- 1.7k
- Avg merge
- 3h 21m
- Merged PRs (30d)
- 873
Description
I decided to try the free models provided by openrouter and found that models.dev has outdated information about them, for example:
-
https://openrouter.ai/deepseek/deepseek-chat-v3-0324:free models.dev does not indicate that this model is free
-
https://openrouter.ai/z-ai/glm-4.5-air:free Openrouter states that the model supports tools, while models.dev states that it does not. But in fact, when I write something to the model to do in opencode, the model calls the tool, but in the wrong format, and nothing happens. I don't know if the problem is in the model or in the missing system prompt for z.ai models, and I also don't know if it is correct to indicate that the model supports/does not support tools
-
https://openrouter.ai/x-ai/grok-4-fast openrouter no longer provides a free version. This update was released just a couple of days ago.
There are many such inconsistencies, which is why I cannot use free models and have to use paid ones. Perhaps it would be worth creating a script/daemon that would get the latest information about models from https://openrouter.ai/api/v1/models, convert it to .toml, and synchronize it with the repository. Its work does not seem resource-intensive, so it can be run every 10 minutes on the server.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by querying the OpenRouter models API at https://openrouter.ai/api/v1/models and compare its responses with the repository's model data and .toml representation. Determine which discrepancies are authoritative, how tool support should be represented, and what synchronization behavior would define the work as complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- ai, api, data
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100