fry69/orw

Watch for changes in OpenRouter models API and store changes in a SQLite database. Includes a simple web interface.

orw: OpenRouter API Watcher

The OpenRouter API Watcher is a tool that monitors changes in OpenRouter models and stores those changes in a SQLite database. It queries the model list via the API every hour and includes a simple web interface for viewing the changes.

Installation

For details how to run the OpenRouter API Watcher as user systemd service, see the INSTALL.

Quick overview: To run the OpenRouter API Watcher, you'll need a recent Node.js (v22). The tools/start.sh script includes the necessary installtion steps (assuming you are running on Mac or Linux):

• install a recent Node.js version via fnm
• install the necessary dependencies via npm
• generate the webclient and server code via tsc
• start the watcher

Note that tools/start.sh will not work if you have not setup a local production environment (see INSTALL).

Web Interface

The OpenRouter API Watcher includes a simple web interface that allows you to view the list of models and the changes that have been detected. By default, the web interface starts on a random, available port. Check the console output for the URL.

RSS feed

The OpenRouter API Watcher also includes a RSS feed generator, available at the /rss endpoint. It will serve the last 50 recorded changes as formatted JSON encapsulated in a <code> tag, so it does not look like a garbled mess in RSS readers.

Testing

You can run a set of simple test cases with the following command:

npm run test

License

This project is licensed under the MIT License.

orw's Issues

bug: removed models showing as a price change to "free"

hey! found this repo through the OR discord, looks slick! love the native RSS support

@spaceemotion brought up a great point about our main site lacking a good changelog for bulk model addition/changes/deletions, and then i remembered seeing your site posted

when we were looking through some of the recent change entries, we noticed that it detected our removal of airoboros as a price change:

after checking our /v1/models api result, i think i see the issue:

confusion probs comes from the fact that when we "remove" a model, we try to keep the model's config visible via API & frontend (for analytics purposes, SEO, etc). usually avoid yoinking the model from the API completely

so when a model is removed from the last provider, it's price will be set to -1

---

happy to try and knock out a quick pr for this here if you think its appropriate! but also feel free to take it on whenever if you would rather that

cheers!