If your app uses model APIs, the release notes and retirement dates are spread across provider docs, changelogs and hosting platforms. A date for one model version or hosting route may not apply to the one you're using. I'm building ModelClock to bring that information together. It tracks LLM and speech model releases, changes, deprecations and published shutdown dates, with a source link and the provider's quoted text attached to each notice. You can browse without an account, keep a watchlist in your browser, and set up Slack/Discord alerts or use RSS and calendar feeds. It's free and currently in beta. The tricky part has been interpreting the source correctly. 'Available until at least this date' is different from 'shutting down on this date,' and a model retiring on one hosting platform doesn't mean it is retiring everywhere. Those distinctions matter more than just putting a countdown on a page. Try it: https://model-clock.com/?utm_source=reddit&utm_campaign=community If you build with model APIs, would you use chat alerts, calendar reminders, or something else to manage these changes? I'd also appreciate feedback on anything that is unclear in the interface.   submitted by   /u/zomenaro [link]   [comments]